Quick answers
- Is CVE-2026-69200 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69200 being exploited in the wild.
- How severe is CVE-2026-69200?
- Low severity, with a CVSS score of 3.7, published 16 September 2026.
- Which products and versions are affected?
- node-opcua node-opcua-client before 2.145.0.
- Is there a fix for CVE-2026-69200?
- A patch was published on 2026-09-16: Version 2.145.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-69200 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-69200?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a prototype pollution flaw (CWE-1321) in the fieldsToJson() method within packages/node-opcua-client/source/alarms_and_conditions/client_alarm.ts. The method directly assigns unsanitized field names to objects using output[field] = value syntax, enabling attackers to inject payloads like "__proto__.pollutedKey" to modify Object.prototype. Exploitation requires an application to pass attacker-controlled event field data to fieldsToJson(); no authentication is required. Successful exploitation may cause denial of service, application logic corruption, or potentially arbitrary code execution if polluted keys reach sensitive code paths. The vulnerability is fixed in node-opcua-client 2.145.0.
Affected products
- node-opcua node-opcua-client before 2.145.0
Timeline
- 2026-07-06: disclosed
- 2026-09-16: patched: Version 2.145.0 released