# CVE-2026-89043: passport-saml-encrypted through 0.1.13 XML Signature Wrapping via Assertion Prepending

> Attackers can bypass SAML authentication by prepending forged assertions, allowing unauthorized access to protected resources.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-8vr8-32m4-xw8q

## What is CVE-2026-89043?

CVE-2026-89043 is a critical authentication bypass vulnerability in krakenjs passport-saml-encrypted, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

passport-saml-encrypted through 0.1.13 contains an XML signature wrapping vulnerability where signature verification and assertion extraction use independent XPath lookups with no cross-validation. Attackers holding any validly signed SAML message can prepend a forged unsigned assertion that gets accepted as the verified identity while the genuine signature validates against the original assertion.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

No fix has been published for CVE-2026-89043 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-89043 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89043 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89043 is a critical authentication bypass vulnerability in krakenjs passport-saml-encrypted, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-89043 exists.

Affected product: krakenjs passport-saml-encrypted. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-89043/ (Markdown: https://insights.sbomify.com/CVE-2026-89043/index.md)
```

## Sources

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

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