NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2020-28441 — conf-cfg-ini

CRITICALFix: loge5/conf-cfg-ini@3a88a6c

CVE-2020-28441 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in conf-cfg-ini. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for conf-cfg-ini — see the affected versions and patch details below.

conf-cfg-ini Prototype Pollution via malicious INI file before v1.2.2

Also known asGHSA-m6mg-jvjf-w44x
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk+0.03%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.24%0.73%1.23%1.72%0.7%1.2%May 26Aug 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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
conf-cfg-ininpm
165downloads / week

Description

This affects the package conf-cfg-ini before 1.2.2. If an attacker submits a malicious INI file to an application that parses it with decode, they will pollute the prototype on the application. This can be exploited further depending on the context.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmconf-cfg-iniall versions1.2.2npm install conf-cfg-ini@1.2.2

Affected Products

1 product · 1 configurations
Application
conf-cfg-iniconf-cfg-ini_project
< 1.2.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 conf-cfg-ini before 1.2.2. If an attacker submi…

security.snyk.ioNVDAug 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update conf-cfg-ini to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28441 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 conf-cfg-ini before 1.2.2. If an attacker submits a malicious INI file to an application that parses it with decode, they will pollute the prototype on the application. This can be exploited further depending on the context.
O3 Security · Impact-Aware SCA

Is CVE-2020-28441 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-28441: conf-cfg-ini — Fixed in 1.2.2