CVE-2020-25125

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 1.3%, top 33% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GnuPG 2.2.21 and 2.2.22 (and Gpg4win 3.1.12) has an array overflow, leading to a crash or possibly unspecified other impact, when a victim imports an attacker's OpenPGP key, and this key has AEAD preferences. The overflow is caused by a g10/key-check.c error. NOTE: GnuPG 2.3.x is unaffected. GnuPG 2.2.23 is a fixed version.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
69%
KEV
Not listed

Published

September 3, 2020

Last Modified

November 21, 2024

References (12)

Affected Packages

(13 across 13 ecosystems)
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.2.23-r0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 154 total refreshes for this CVE.

  1. 2026-09-18 19:23 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-17 19:22 UTCEPSS rescore
  4. 2026-09-16 14:04 UTCEPSS rescore
  5. 2026-09-15 03:06 UTCEPSS rescore
  6. 2026-09-15 03:06 UTCEPSS rescore
  7. 2026-09-13 16:42 UTCEPSS rescore
  8. 2026-09-12 14:56 UTCEPSS rescore
  9. 2026-09-11 14:48 UTCEPSS rescore
  10. 2026-09-11 09:32 UTCEPSS rescore
  11. 2026-09-10 09:29 UTCEPSS rescore
  12. 2026-09-08 21:56 UTCEPSS rescore
  13. 2026-09-07 15:57 UTCEPSS rescore
  14. 2026-09-07 03:17 UTCOSV refresh
  15. 2026-09-06 13:44 UTCEPSS rescore
  16. 2026-09-05 15:24 UTCEPSS rescore
  17. 2026-09-04 13:57 UTCEPSS rescore
  18. 2026-09-04 05:03 UTCEPSS rescore
  19. 2026-09-02 14:08 UTCEPSS rescore
  20. 2026-08-30 19:14 UTCEPSS rescore
  21. 2026-08-30 01:18 UTCEPSS rescore
  22. 2026-08-27 14:21 UTCEPSS rescore
  23. 2026-08-26 14:42 UTCEPSS rescore
  24. 2026-08-25 13:45 UTCEPSS rescore
  25. 2026-08-21 23:45 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:52 UTCEPSS rescore
  2. 2026-08-20 13:01 UTCOSV refresh
  3. 2026-08-19 17:00 UTCEPSS rescore
  4. 2026-08-18 13:44 UTCEPSS rescore
  5. 2026-08-16 14:52 UTCEPSS rescore
  6. 2026-08-16 02:11 UTCEPSS rescore
  7. 2026-08-15 01:26 UTCEPSS rescore
  8. 2026-08-13 21:57 UTCEPSS rescore
  9. 2026-08-12 13:47 UTCEPSS rescore
  10. 2026-08-09 13:43 UTCEPSS rescore
  11. 2026-08-08 16:33 UTCEPSS rescore
  12. 2026-08-07 16:23 UTCEPSS rescore
  13. 2026-08-06 13:43 UTCEPSS rescore
  14. 2026-08-05 19:14 UTCEPSS rescore
  15. 2026-08-05 08:10 UTCOSV refresh
  16. 2026-08-04 15:06 UTCEPSS rescore
  17. 2026-08-04 10:34 UTCEPSS rescore
  18. 2026-08-03 10:32 UTCEPSS rescore
  19. 2026-08-02 02:23 UTCEPSS rescore
  20. 2026-08-01 04:12 UTCEPSS rescore
  21. 2026-07-30 16:25 UTCEPSS rescore
  22. 2026-07-30 01:27 UTCEPSS rescore
  23. 2026-07-28 15:32 UTCEPSS rescore
  24. 2026-07-27 14:06 UTCEPSS rescore
  25. 2026-07-26 14:51 UTCEPSS rescore
  26. 2026-07-25 14:15 UTCEPSS rescore
  27. 2026-07-25 14:14 UTCEPSS rescore
  28. 2026-07-24 14:14 UTCEPSS rescore
  29. 2026-07-23 14:15 UTCEPSS rescore
  30. 2026-07-23 14:15 UTCEPSS rescore
  31. 2026-07-23 01:51 UTCEG score recompute
  32. 2026-07-22 22:37 UTCEG score recompute
  33. 2026-07-22 14:05 UTCEPSS rescore
  34. 2026-07-21 15:22 UTCEPSS rescore
  35. 2026-07-21 15:22 UTCEPSS rescore
  36. 2026-07-20 17:04 UTCEPSS rescore
  37. 2026-07-20 17:04 UTCEPSS rescore
  38. 2026-07-19 14:28 UTCEPSS rescore
  39. 2026-07-19 06:52 UTCOSV refresh
  40. 2026-07-19 02:26 UTCEPSS rescore
  41. 2026-07-19 02:26 UTCEPSS rescore
  42. 2026-07-18 10:02 UTCEPSS rescore
  43. 2026-07-16 16:59 UTCEPSS rescore
  44. 2026-07-15 16:55 UTCEPSS rescore
  45. 2026-07-15 01:57 UTCEPSS rescore
  46. 2026-07-13 22:27 UTCEPSS rescore
  47. 2026-07-13 22:27 UTCEPSS rescore
  48. 2026-07-13 06:10 UTCEPSS rescore
  49. 2026-07-13 06:10 UTCEPSS rescore
  50. 2026-07-12 05:44 UTCEPSS rescore
  51. 2026-07-11 08:25 UTCEPSS rescore
  52. 2026-07-11 08:25 UTCEPSS rescore
  53. 2026-07-09 19:07 UTCEPSS rescore
  54. 2026-07-08 15:12 UTCEPSS rescore
  55. 2026-07-07 13:43 UTCEPSS rescore
  56. 2026-07-07 13:43 UTCEPSS rescore
  57. 2026-07-06 16:25 UTCEPSS rescore
  58. 2026-07-06 16:25 UTCEPSS rescore
  59. 2026-07-06 02:21 UTCEPSS rescore
  60. 2026-07-06 02:21 UTCEPSS rescore
  61. 2026-07-05 02:27 UTCEPSS rescore
  62. 2026-07-04 06:29 UTCEPSS rescore
  63. 2026-07-04 06:28 UTCEPSS rescore
  64. 2026-07-01 15:03 UTCEPSS rescore
  65. 2026-07-01 12:46 UTCOSV refresh
  66. 2026-06-30 23:20 UTCEPSS rescore
  67. 2026-06-30 23:20 UTCEPSS rescore
  68. 2026-06-29 14:04 UTCEPSS rescore
  69. 2026-06-28 14:05 UTCEPSS rescore
  70. 2026-06-28 04:54 UTCEPSS rescore
  71. 2026-06-28 04:54 UTCEPSS rescore
  72. 2026-06-27 03:06 UTCEPSS rescore
  73. 2026-06-25 13:47 UTCEPSS rescore
  74. 2026-06-24 14:03 UTCEPSS rescore
  75. 2026-06-24 14:03 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-25125?
CVE-2020-25125 is a high vulnerability published on September 3, 2020. GnuPG 2.2.21 and 2.2.22 (and Gpg4win 3.1.12) has an array overflow, leading to a crash or possibly unspecified other impact, when a victim imports an attacker's OpenPGP key, and this key has AEAD preferences. The overflow is caused by a g10/key-check.c error. NOTE: GnuPG 2.3.x is unaffected. GnuPG…
When was CVE-2020-25125 disclosed?
CVE-2020-25125 was first published in the National Vulnerability Database on September 3, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-25125 actively exploited?
CVE-2020-25125 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 31.2% of all scored CVEs.
What is the CVSS score of CVE-2020-25125?
CVE-2020-25125 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2020-25125?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-25125, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2020-25125?

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

Start Free Scan →Browse All CVEs