CVE-2020-7788

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 3.7% (89th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2020-12-10) is not newer than that change (2026-10-08), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2020-1502 (ENISA EUVD) · GHSA-qqgx-2p2h-9c37 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation3.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
3.7%
EPSS %ILE
89th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
3.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 11, 2020

Last Modified

October 8, 2026

Advisory Details (3)

Auto-updated Nov 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit.
Web page🟡 PoC Available

Prototype Pollution in ini | CVE-2020-7788 | Snyk

https://snyk.io/vuln/SNYK-JS-INI-1048974
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2503-1] node-ini security update

https://lists.debian.org/debian-lts-announce/2020/12/msg00032.html
GitHub commit Patch Available

commit 56d2805e07cc (npm/ini)

Patch available: npm/ini v3.0.0 (contains commit 56d2805e07cc)

https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs-nodemon-0:2.0.19-1.el9_02022-09-20redhat
redhatnodejs:14-8050020211213115342.c53685002022-02-01redhat
redhatnodejs:14-8040020211213111158.522a0ee42022-01-25redhat
redhatnodejs:16-8050020211206113934.c53685002021-12-16redhat
redhatrh-nodejs14-nodejs-nodemon-0:2.0.3-5.el72021-08-26redhat
redhatrh-nodejs12-nodejs-nodemon-0:2.0.3-5.el72021-08-26redhat
redhatnodejs:10-8030020210118191659.229f0a1c2021-02-16redhat
redhatnodejs:12-8030020210129141730.229f0a1c2021-02-16redhat
redhatnodejs:14-8030020210126165503.229f0a1c2021-02-16redhat
redhatrh-nodejs10-nodejs-0:10.23.1-2.el72021-02-15redhat
redhatrh-nodejs12-nodejs-nodemon-0:2.0.3-1.el72021-02-11redhat
redhatrh-nodejs14-nodejs-0:14.15.4-2.el72021-02-04redhat
npmini @ 1.3.6 (fixes < 1.3.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-ini—
  • every version up to 2.0.0-1: fixed in 2.0.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-ini—
  • every version up to 2.0.0-1: fixed in 2.0.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-ini—
  • every version up to 2.0.0-1: fixed in 2.0.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-ini—
  • every version up to 2.0.0-1: fixed in 2.0.0-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
node-ini1.1.0-1
  • every version up to 1.1.0-1+deb9u1: fixed in 1.1.0-1+deb9u1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
ini—
  • every version up to 1.3.6: fixed in 1.3.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 70× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 284 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 184 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 06:06 UTCEchelonGraph re-scored
  2. 2026-11-13 06:06 UTCVendor advisory
  3. 2026-11-13 06:06 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  4. 2026-11-12 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  5. 2026-11-12 04:26 UTCEchelonGraph re-scored
  6. 2026-11-12 04:26 UTCVendor advisory
  7. 2026-11-12 04:26 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  8. 2026-11-11 16:31 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  9. 2026-11-11 02:45 UTCEchelonGraph re-scored
  10. 2026-11-11 02:45 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  11. 2026-11-10 16:34 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  12. 2026-11-10 00:46 UTCEchelonGraph re-scored
  13. 2026-11-10 00:46 UTCVendor advisory
  14. 2026-11-10 00:46 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  15. 2026-11-09 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  16. 2026-11-08 23:09 UTCEchelonGraph re-scored
  17. 2026-11-08 23:09 UTCVendor advisory
  18. 2026-11-08 23:09 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-11-08 16:32 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  20. 2026-11-07 21:31 UTCEchelonGraph re-scored
  21. 2026-11-07 21:31 UTCVendor advisory
  22. 2026-11-07 21:31 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-11-07 16:33 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  24. 2026-11-06 19:52 UTCEchelonGraph re-scored
  25. 2026-11-06 19:52 UTCVendor advisory
Show 75 more
  1. 2026-11-06 19:52 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  2. 2026-11-06 16:30 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  3. 2026-11-05 18:14 UTCEchelonGraph re-scored
  4. 2026-11-05 18:14 UTCVendor advisory
  5. 2026-11-05 18:14 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  6. 2026-11-05 16:30 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  7. 2026-11-04 16:36 UTCEchelonGraph re-scored
  8. 2026-11-04 16:36 UTCVendor advisory
  9. 2026-11-04 16:36 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  10. 2026-11-04 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  11. 2026-11-03 16:37 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  12. 2026-11-03 14:58 UTCEchelonGraph re-scored
  13. 2026-11-03 14:58 UTCVendor advisory
  14. 2026-11-03 14:58 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  15. 2026-11-03 13:55 UTCOSV refresh
  16. 2026-11-02 13:16 UTCEchelonGraph re-scored
  17. 2026-11-02 13:16 UTCVendor advisory
  18. 2026-11-02 13:16 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-11-01 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  20. 2026-11-01 11:36 UTCVendor advisory
  21. 2026-11-01 11:36 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  22. 2026-11-01 08:35 UTCGHSA enrichmentGHSA-qqgx-2p2h-9c37 · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-11-01 08:35 UTCEchelonGraph re-scored
  24. 2026-10-31 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  25. 2026-10-31 09:58 UTCEchelonGraph re-scored
  26. 2026-10-31 09:58 UTCVendor advisory
  27. 2026-10-30 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  28. 2026-10-30 08:21 UTCEchelonGraph re-scored
  29. 2026-10-30 08:21 UTCVendor advisory
  30. 2026-10-29 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  31. 2026-10-29 06:44 UTCEchelonGraph re-scored
  32. 2026-10-29 06:44 UTCVendor advisory
  33. 2026-10-28 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  34. 2026-10-28 05:04 UTCEchelonGraph re-scored
  35. 2026-10-28 05:04 UTCVendor advisory
  36. 2026-10-27 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  37. 2026-10-27 03:27 UTCEchelonGraph re-scored
  38. 2026-10-27 03:27 UTCVendor advisory
  39. 2026-10-26 16:27 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  40. 2026-10-25 21:43 UTCVendor advisory
  41. 2026-10-25 18:39 UTCEchelonGraph re-scored
  42. 2026-10-25 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  43. 2026-10-24 19:49 UTCEchelonGraph re-scored
  44. 2026-10-24 19:49 UTCVendor advisory
  45. 2026-10-24 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  46. 2026-10-23 18:12 UTCEchelonGraph re-scored
  47. 2026-10-23 18:12 UTCVendor advisory
  48. 2026-10-23 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  49. 2026-10-22 16:29 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  50. 2026-10-22 16:18 UTCEchelonGraph re-scored
  51. 2026-10-22 16:18 UTCVendor advisory
  52. 2026-10-21 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  53. 2026-10-21 14:22 UTCEchelonGraph re-scored
  54. 2026-10-21 14:22 UTCVendor advisory
  55. 2026-10-20 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  56. 2026-10-20 12:45 UTCEchelonGraph re-scored
  57. 2026-10-20 12:45 UTCVendor advisory
  58. 2026-10-19 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  59. 2026-10-19 11:06 UTCEchelonGraph re-scored
  60. 2026-10-19 11:06 UTCVendor advisory
  61. 2026-10-18 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  62. 2026-10-18 08:09 UTCEchelonGraph re-scored
  63. 2026-10-18 08:09 UTCVendor advisory
  64. 2026-10-17 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  65. 2026-10-17 06:29 UTCEchelonGraph re-scored
  66. 2026-10-17 06:29 UTCVendor advisory
  67. 2026-10-16 16:33 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  68. 2026-10-16 04:51 UTCEchelonGraph re-scored
  69. 2026-10-16 04:51 UTCVendor advisory
  70. 2026-10-15 16:27 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  71. 2026-10-15 03:11 UTCEchelonGraph re-scored
  72. 2026-10-15 03:11 UTCVendor advisory
  73. 2026-10-14 16:28 UTCEPSS rescoreEPSS 3.7% · 89th percentile
  74. 2026-10-13 23:23 UTCEchelonGraph re-scored
  75. 2026-10-13 23:23 UTCVendor advisory

Frequently asked(5)

What is CVE-2020-7788?
CVE-2020-7788 is a critical-severity vulnerability; its CVE record was published on December 11, 2020. This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
When was CVE-2020-7788 made public?
CVE-2020-7788 was made public on December 11, 2020: that is the date its CVE record's CNA, Snyk, gives for when the vulnerability was made public. The CVE record itself was published on December 11, 2020. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2020-7788 actively exploited?
CVE-2020-7788 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% probability of exploitation in the next 30 days (89th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-7788?
CVE-2020-7788 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2020-7788?
A fix for CVE-2020-7788 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-7788 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-7788

Explore →

Is Your Infrastructure Affected by CVE-2020-7788?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.