Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-5379-r78w-42h2

MEDIUM

Unlimited transforms allowed for signed nodes

Also known asCVE-2021-39171
Published
Aug 30, 2021
Updated
Mar 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk67th percentile+0.86%
0.00%0.61%1.22%1.82%0.5%1.3%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

passport-samlnpm
144Kdownloads / week

Description

Impact

A malicious SAML payload can require transforms that consume significant system resources to process, thereby resulting in reduced or denied service. This would be an effective way to perform a denial-of-service attack.

Patches

This has been resolved in version 3.1.0. The resolution is to limit the number of allowable transforms to 2.

References

https://github.com/node-saml/passport-saml/pull/595

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmpassport-samlall versions3.1.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for passport-saml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update passport-saml to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5379-r78w-42h2 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-5379-r78w-42h2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5379-r78w-42h2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A malicious SAML payload can require transforms that consume significant system resources to process, thereby resulting in reduced or denied service. This would be an effective way to perform a denial-of-service attack. ### Patches This has been resolved in version 3.1.0. The resolution is to limit the number of allowable transforms to 2. ### References https://github.com/node-saml/passport-saml/pull/595
O3 Security · Impact-Aware SCA

Is GHSA-5379-r78w-42h2 in your dependencies?

O3 detects GHSA-5379-r78w-42h2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.