Skip to main content
Menu
CVEs

soap prototype pollution in WSDL.xmlToObject

CVE-2026-133243EUVD-2026-130313Published November 19, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.14.1
Who is exposed
Not reported

Summary

The node-soap package from vpulim has a prototype pollution flaw in its WSDL.xmlToObject function. A remote, unauthenticated attacker can send one crafted SOAP request with an XML element whose id is "__proto__" to a soap.listen() server, or return a malicious response to a client, which pollutes Object.prototype and makes all later SOAP parsing fail until the process restarts.

Written by a model

Original description

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.

Who should check

Teams running the npm package node-soap before 1.14.1, as a SOAP server (soap.listen) or as a SOAP client

“Affecting node-soap >= 0, < 1.14.1”

vulncheck.com

What to do

Upgrade to a fixed version: 1.14.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133243 (node-soap before 1.14.1 Prototype Pollution via multiRef id in WSDL.xmlToObject), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133243 (entry last updated 2026-11-19):
Affected:
- npm package soap: fixed in 1.14.1
Fixed versions: 1.14.1.
Conditions (all must be true for the bug to be hit):
- node-soap versions before 1.14.1 (source: https://www.vulncheck.com/advisories/node-soap-before-1.14.1-prototype-pollution-via-multiref-id-in-wsdl-xmltoobject)
- A crafted XML element with id="__proto__" is parsed, in a SOAP request to a soap.listen() server or in a SOAP response to a client (source: https://www.vulncheck.com/advisories/node-soap-before-1.14.1-prototype-pollution-via-multiref-id-in-wsdl-xmltoobject)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133243 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133243 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/vpulim/node-soap/pull/1542
- https://github.com/vpulim/node-soap/commit/7812a076d3913064d6ee8e7e2a1cb6a30ea832dd
- https://github.com/vpulim/node-soap/releases/tag/v1.14.1
- https://github.com/vpulim/node-soap/blob/v1.14.0/src/wsdl/index.ts#L213
- https://github.com/vpulim/node-soap/blob/v1.14.0/src/wsdl/index.ts#L520-L527
- https://github.com/vpulim/node-soap
- https://www.vulncheck.com/advisories/node-soap-before-1.14.1-prototype-pollution-via-multiref-id-in-wsdl-xmltoobject
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133243
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133243"}.

Affected versions

cve.now Index

45Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach16/20soap: 1.5M downloads a week
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 9

Questions about CVE-2026-133243

Is CVE-2026-133243 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A crafted XML element with id="__proto__" is parsed by node-soap, which pollutes Object.prototype. After that, all later SOAP parsing fails until the process restarts, causing a denial of service.

Source: vulncheck.com

Which versions are affected by CVE-2026-133243?

soap (npm): before 1.14.1.

Source: cve.now feed data

Am I affected, and how do I check?

Affected are node-soap versions before 1.14.1. The crafted element can arrive in a SOAP request to a soap.listen() server or in a SOAP response to a client. To check, look at the node-soap version in your project's package.json or installed dependencies.

Source: vulncheck.com

How do I fix CVE-2026-133243?

Upgrade node-soap to 1.14.1 or later, which contains the fix.

Source: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.