CVE-2026-133243 in node-soap
Summary
by MITRE • 11/20/2026
node-soap before 1.14.1 contains a prototype pollution vulnerability in WSDL.xmlToObject that allows unauthenticated attackers to pollute Object.prototype via an XML element with id="__proto__". Attackers can send a single crafted SOAP request to a soap.listen() server, or return a malicious response to a client, causing all subsequent SOAP parsing to fail until process restart.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in node-soap versions prior to 1.14.1 represents a critical prototype pollution flaw located within the WSDL.xmlToObject function. This security issue stems from how the library processes XML elements during the conversion of Web Services Description Language data into JavaScript objects. Specifically, when an attacker supplies an XML element with the identifier _proto_, the underlying logic fails to properly sanitize or restrict this input before merging it into the target object structure. In JavaScript environments that utilize prototype-based inheritance, such as Node.js and modern browsers, every object inherits properties from a central Object.prototype unless explicitly isolated. By injecting a property named _proto_ through an XML payload, the attacker effectively manipulates the prototype chain of newly created objects rather than just setting a standard property on the immediate instance.
This mechanism allows unauthenticated attackers to pollute the global Object.prototype with arbitrary data or malicious code snippets embedded within the SOAP request body. The impact is severe because once the prototype is polluted, every subsequent object instantiated in the application inherits these corrupted properties. In the context of node-soap, this corruption disrupts the internal parsing logic and property access patterns expected by the library. Consequently, all future attempts to parse SOAP messages will fail, leading to a denial of service condition for any client or server relying on that specific process instance. The system does not crash in a traditional sense but becomes functionally broken until the Node.js process is restarted, effectively taking down the associated web services indefinitely without requiring further exploitation steps from the attacker.
From an industry standard perspective, this vulnerability aligns with CWE-1325, which covers Incorrect Check for Unusual or Exceptional Conditions related to prototype pollution, and more broadly falls under CWE-915 Improper Modification of Objects with Modifiable Prototypes. In terms of tactical classification within the MITRE ATT&CK framework, this behavior is consistent with Taint Analysis failures often seen in injection attacks where untrusted data influences control flow or state without proper validation. The attack vector is classified as Network-based because it requires sending a crafted SOAP request over HTTP/S to a listening endpoint that utilizes node-soap for parsing incoming messages.
Mitigation strategies must prioritize immediate version upgrades and defensive coding practices. Organizations running affected versions of node-soap should upgrade to version 1.14.1 or later, where the vulnerability has been patched by implementing stricter checks on property names during object construction. Developers utilizing older versions that cannot be immediately upgraded should implement input validation middleware to strip or reject XML elements containing _proto_, constructor, or other reserved prototype keys before they reach the parsing logic. Additionally, employing Object.create(null) for intermediate objects can isolate them from the global prototype chain, providing a layer of defense against such pollution attempts even if the underlying library remains vulnerable. Regular security audits and dependency scanning tools should be employed to detect these types of supply chain vulnerabilities early in the development lifecycle.