CVE-2025-68972

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2025-12-28. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: Elevated riskExposed: 0

A fix is available — apply it.

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

CVSS v3
5.9
EG Score
5.9(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

December 27, 2025

Last Modified

January 9, 2026

Advisory Details (3)

Auto-updated Aug 8, 2026
No patch confirmed yet.
generic

gpg.fail

https://gpg.fail/formfeed
generic

A thru-line of some of the gnarliest vulnerabilities here is PGP's insane packet... | Hacker News

https://news.ycombinator.com/item?id=46404339
generic

To sign or not to sign: Practical vulnerabilities in GPG & friends - media.ccc.de

https://media.ccc.de/v/39c3-to-sign-or-not-to-sign-practical-vulnerabilities-i

Vendor Advisories for CVE-2025-68972(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgnupg2-main-2.4.9-5.1.hum12026-04-10redhat

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.4.9-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.4.9-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.4.9-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.4.9-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
gnupg—2.4.9-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gnupg22.2.27-2 ... 2.4.9-7 (80 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
gnupg22.2.40-1.1 ... 2.4.9-7 (70 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gnupg22.4.7-21 ... 2.4.9-7 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gnupg22.4.7-21 ... 2.4.9-7 (14 versions)——

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 7× in last 7d / 26× 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 135 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-68972?
CVE-2025-68972 is a medium vulnerability published on December 27, 2025. In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed…
When was CVE-2025-68972 disclosed?
CVE-2025-68972 was first published in the National Vulnerability Database on December 27, 2025, with the most recent update on January 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68972 actively exploited?
CVE-2025-68972 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2025-68972?
CVE-2025-68972 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2025-68972?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68972, 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-2025-68972

Explore →

Is Your Infrastructure Affected by CVE-2025-68972?

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

Start Free Scan →Browse All CVEs