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

Prototype pollution in multi-iniGHSA-67mq-h2r9-rh2m

MEDIUMFix: evangelion1204/multi-ini@6b2212b

GHSA-67mq-h2r9-rh2m is a medium-severity (CVSS 5.6) CWE-1321 vulnerability in multi-ini. 1 public exploit reference exists, so weaponization risk is real. A fix is available for multi-ini — see the affected versions and patch details below.

Also known asCVE-2020-28460SNYK-JS-MULTIINI-1053229
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.03%0.70%1.37%2.04%0.5%1.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-67mq-h2r9-rh2m 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.

13other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
multi-ininpm
2Kdownloads / week

Description

This affects the package multi-ini before 2.1.2. It is possible to pollute an object's prototype by specifying the constructor.proto object as part of an array. This is a bypass of CVE-2020-28448.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmulti-iniall versions2.1.2npm install multi-ini@2.1.2

Affected Products

1 product · 1 configurations
Application
multi-inimulti-ini_project
< 2.1.2
range
Exploits & PoCs
1

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

This affects the package multi-ini before 2.1.2. It is possible to pollu…

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

  2. Fix

    Update multi-ini to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67mq-h2r9-rh2m 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.

Frequently Asked Questions

This affects the package multi-ini before 2.1.2. It is possible to pollute an object's prototype by specifying the constructor.proto object as part of an array. This is a bypass of CVE-2020-28448.
O3 Security · Impact-Aware SCA

Is GHSA-67mq-h2r9-rh2m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Prototype pollution in multi-ini (Medium 5.6)