Summary
Passport-wsfed-saml2 allows SAML Authentication Bypass via Attribute Smuggling
Overview
This vulnerability allows an attacker to impersonate any user during SAML authentication by tampering with a valid SAML response. This can be done by adding attributes to the response.
Am I Affected?
You are affected by this SAML Attribute Smuggling vulnerability if you are using passport-wsfed-saml2 version 4.6.3 or below, specifically under the following conditions:
- The service provider is using
passport-wsfed-saml2, - A valid SAML Response signed by the Identity Provider can be obtained
Impact
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to v4.6.4 or greater.
Frequently Asked Questions
- What is CVE-2025-46573? CVE-2025-46573 is a high-severity improper authentication vulnerability in passport-wsfed-saml2 (npm), affecting versions >= 3.0.5, <= 4.6.3. It is fixed in 4.6.4. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which versions of passport-wsfed-saml2 are affected by CVE-2025-46573? passport-wsfed-saml2 (npm) versions >= 3.0.5, <= 4.6.3 is affected.
- Is there a fix for CVE-2025-46573? Yes. CVE-2025-46573 is fixed in 4.6.4. Upgrade to this version or later.
- Is CVE-2025-46573 exploitable, and should I be worried? Whether CVE-2025-46573 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-46573 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-46573? Upgrade
passport-wsfed-saml2to 4.6.4 or later.