passport-wsfed-saml2 Signature Bypass vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Information Please note that this is not a new disclosure, and is previously reported in our SECURITY-NOTICE.md which we removed in favor of github advisory. Overview A vulnerability was found in the validation of a SAML signature. The validation doesn't ensure that the "Signature" tag is at the proper location inside an "Assertion" tag. This leads to a signature relocation attack where the attacker can corrupt one field of data while maintaining the signature valid. This could allow an authenticated attacker to "remove" one group from the assertion or corrupt another field of an assertion. Am I affected? You are affected if you are using the passport-wsfed-saml2 library to version < 3.0.10 How do I fix it? You may fix this issue by upgrading passport-wsfed-saml2 library to version 3.0.10 or above. Will the fix impact my users? This fix patches the library that your application runs, but will not impact your users, their current state, or any existing sessions.

Published by the source

21 Jun 2023, 22:06 UTC

Last modified by the source

21 Jun 2023, 22:06 UTC

Source last checked

26 Oct 2026, 12:22 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5wrg-8fxp-cx9r

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5wrg-8fxp-cx9r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-5wrg-8fxp-cx9r

Advisory: passport-wsfed-saml2 Signature Bypass vulnerability
IDs: GHSA-5wrg-8fxp-cx9r
Record: https://patchnext.com/advisories/ghsa-5wrg-8fxp-cx9r (revision 2, source checked 26 Oct 2026, 12:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: passport-wsfed-saml2 3.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm passport-wsfed-saml2: affected < 3.0.10; fixed in 3.0.10

## Suggested inspection (read-only)
- `npm ls passport-wsfed-saml2 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on passport-wsfed-saml2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5wrg-8fxp-cx9r (OSV record GHSA-5wrg-8fxp-cx9r lists affected ranges: npm passport-wsfed-saml2 >=0 <3.0.10 (fixed))
- Verified: https://github.com/advisories/GHSA-5wrg-8fxp-cx9r (GitHub-reviewed advisory GHSA-5wrg-8fxp-cx9r lists affected ranges: npm passport-wsfed-saml2 >=0 <3.0.10)

Commands are suggestions: review each one before running it.