node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarms_and_conditions/client_alarm.ts directly assigns unsanitized field names and allows a __proto__.pollutedKey path to modify Object.prototype. Successful exploitation requires an application to expose attacker-controlled event fields to fieldsToJson and may cause denial of service or application logic corruption. This vulnerability is fixed in 2.145.0.
CVE-2026-69200
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
References (2)
- security-advisories@githubhttps://github.com/node-opcua/node-opcua/security/advisories/GHSA-cv5q-7543-48q4
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/node-opcua/node-opcua/security/advisories/GHSA-cv5q-7543-48q4
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:32 UTCEG score recompute
- 2026-09-18 18:15 UTCEG score recompute
- 2026-09-16 17:36 UTCEG score recompute
- 2026-09-16 16:22 UTCEG score recompute
- 2026-09-16 16:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-1321
- CVE-2020-12079EG 10.0CRITICAL
- CVE-2011-10019EG 9.8EPSS p90CRITICAL
- CVE-2020-28462NVD 7.3EG 9.8CRITICAL
- CVE-2020-28276EG 9.8CRITICAL
- CVE-2020-28271EG 9.8CRITICAL
- CVE-2020-28270EG 9.8EPSS p90CRITICAL
- CVE-2020-28269EG 9.8EPSS p90CRITICAL
- CVE-2020-8158EG 9.8CRITICAL
- CVE-2019-0230EG 9.8EPSS p100CRITICAL
- CVE-2020-7727EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-69200?
When was CVE-2026-69200 disclosed?
Is CVE-2026-69200 actively exploited?
What is the CVSS score of CVE-2026-69200?
How do I remediate CVE-2026-69200?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-69200
Is Your Infrastructure Affected by CVE-2026-69200?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.