Improper Verification of Cryptographic Signature The advisory has been revoked - it doesn't affect any version of package gnupg (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-UNMANAGED-GNUPG-14723287
- published28 Dec 2025
- disclosed27 Dec 2025
- creditUnknown
Introduced: 27 Dec 2025
CVE-2025-68972 (opens in a new tab)Amendment
This was deemed not a vulnerability.
Overview
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature via the handling of plaintext lines containing a \f character. An attacker can append unauthorized content to the signed material by crafting a special message that contains a \f at the end of a line, causing signature verification to succeed on the altered message.
Note:
According to the vendor, this is not a security vulnerability (social engineering, improper use of cleartext signatures, and UI changes would be required). Signature verification itself is correct. Any difference is a result of comparing the wrong output.
For the full details see GnuPG Statement.