How severe is CVE-2022-39299?

CVE-2022-39299 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-39299?

CVE-2022-39299 affects the following packages: passport-saml (npm), node-saml (npm), @node-saml/node-saml (npm), @node-saml/passport-saml (npm). Ecosystems affected: npm.

How do I fix CVE-2022-39299?

Update passport-saml to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39299 is resolved across your whole dependency graph.

How do I detect CVE-2022-39299 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passport-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-39299 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-39299 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2022-39299, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-39299?

CVE-2022-39299 has an EPSS (Exploit Prediction Scoring System) score of 4.5%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-39299?

CVE-2022-39299 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-39299 published, and has it been updated?

CVE-2022-39299 was published on October 12, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

CVE-2022-39299 — passport-saml

HIGHFix: node-saml/passport-saml@8b7e3f5

CVE-2022-39299 is a high-severity (CVSS 7.4) CWE-347 vulnerability in passport-saml. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for passport-saml — see the affected versions and patch details below.

Signature bypass via multiple root elements in Passport-SAML

Also known asGHSA-m974-647v-whv7

Published

Oct 12, 2022

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

2 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-39299.

EPSS Exploitation Probability

via FIRST.org ↗

4.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

passport-samlnpm

86Kdownloads / week

node-samlnpm

3Kdownloads / week

@node-saml/node-samlnpm

2.0Mdownloads / week

Description

Impact

A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered.

Patches

Users should upgrade to passport-saml 3.2.2 or newer. The issue was also present in the beta releases of node-saml before v4.0.0-beta.5.

Workarounds

Disable SAML authentication.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Open a discussion in the node-saml repo

Credits

Felix Wilhelm of Google Project Zero

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`passport-saml`	all versions	3.2.2`npm install passport-saml@3.2.2`
📦npm	`node-saml`	all versions	4.0.0-beta.5`npm install node-saml@4.0.0-beta.5`
📦npm	`@node-saml/node-saml`	all versions	4.0.0-beta.5`npm install @node-saml/node-saml@4.0.0-beta.5`
📦npm	`@node-saml/passport-saml`	all versions	4.0.0-beta.3`npm install @node-saml/passport-saml@4.0.0-beta.3`

Affected Products

1 product · 5 configurations

Application

passport-samlpassport-saml_project

< 3.2.2

1 version

4.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Passport-SAML is a SAML 2.0 authentication provider for Passport, the No…

github.comGithubOct 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passport-saml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update passport-saml to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39299 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact A remote attacker may be able to bypass SAML authentication on a website using passport-saml. A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered. ### Patches Users should upgrade to passport-saml 3.2.2 or newer. The issue was also present in the beta releases of `node-saml` before v4.0.0-beta.5. ### Workarounds Disable SAML authentication. ### References _Are