# CVE-2026-133243: node-soap before 1.14.1 Prototype Pollution via multiRef id in WSDL.xmlToObject


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-572r-wcgw-fhp3

## What is CVE-2026-133243?

CVE-2026-133243 is a high-severity vulnerability in vpulim node-soap, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-133243?

1 open source package ship an affected version, including soap.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `soap` | npm | `pkg:npm/soap` | All versions | 1.14.1 |

## How do I fix CVE-2026-133243?

Upgrade each affected package to the fixed version listed for it above. Each package has its own fixed versions.

## Is CVE-2026-133243 being exploited?

There is no known exploitation of CVE-2026-133243 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133243 and fix it if it is affected.

What it is: CVE-2026-133243 is a high-severity vulnerability in vpulim node-soap, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133243 in the wild and no public exploit code.

Affected packages and fixed versions:
- soap (npm): affected all versions; fixed in 1.14.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133243/ (Markdown: https://insights.sbomify.com/CVE-2026-133243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133243
- OSV: https://osv.dev/vulnerability/CVE-2026-133243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133243/
Summaries are generated and may contain mistakes; the official description above is the record.
