Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Prototype PollutionGHSA-x3wr-v4wx-5qpc

CRITICAL

GHSA-x3wr-v4wx-5qpc is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in expand-hash. 2 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Also known asCVE-2021-25948
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
2 known
Exploitation data as of Oct 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
2.45%2.90%3.35%3.80%2.9%3.3%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-x3wr-v4wx-5qpc by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
expand-hashnpm
868downloads / week

Description

Prototype pollution vulnerability in ‘expand-hash’ versions 0.1.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmexpand-hashall versionsNo fix

Affected Products

1 product · 1 configurations
Application
expand-hashexpand-hash_project
≥ 0.1.0 && ≤ 1.0.1
range
Exploits & PoCs
2

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

Prototype pollution vulnerability in 'expand-hash' versions 0.1.0 throug…

whitesourcesoftware.comNVDJun 2021

Prototype pollution vulnerability in 'expand-hash' versions 0.1.0 throug…

github.comNVDJun 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Remediation status

    No patched version of expand-hash has shipped for GHSA-x3wr-v4wx-5qpc yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Prototype pollution vulnerability in ‘expand-hash’ versions 0.1.0 through 1.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.
O3 Security · Impact-Aware SCA

Is GHSA-x3wr-v4wx-5qpc in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Prototype Pollution (Critical 9.8)