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

Prototype Pollution in config-handlerGHSA-2w3f-9w3q-qw77

CRITICAL

GHSA-2w3f-9w3q-qw77 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in config-handler. 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-23448SNYK-JS-CONFIGHANDLER-1564947
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
2 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.56%1.13%1.69%0.4%1.2%May 26Aug 26Oct 26

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

How urgent is this, really

GHSA-2w3f-9w3q-qw77 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
config-handlernpm
262downloads / week

Description

All versions of package config-handler are vulnerable to Prototype Pollution when loading config files.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmconfig-handlerall versionsNo fix

Affected Products

1 product · 1 configurations
Application
config-handlerconfig-handler_project
1 version
1.0.0
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.

All versions of package config-handler are vulnerable to Prototype Pollu…

github.comNVDOct 2021

All versions of package config-handler are vulnerable to Prototype Pollu…

snyk.ioNVDOct 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 config-handler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of config-handler has shipped for GHSA-2w3f-9w3q-qw77 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

    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

All versions of package config-handler are vulnerable to Prototype Pollution when loading config files.
O3 Security · Impact-Aware SCA

Is GHSA-2w3f-9w3q-qw77 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Prototype Pollution in config-handler (Critical 9.8)