# CVE-2025-68972: Security feature bypass in GnuPG

> An attacker can append text to signed messages by exploiting form feed handling, bypassing signature verification integrity checks.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2025
- **Updated:** 2 Jan 2026
- **Also known as:** ALPINE-CVE-2025-68972, AZL-73192, AZL-73911, BELL-CVE-2025-68972, DEBIAN-CVE-2025-68972, GHSA-w789-3q45-984r, JLSEC-2026-562, MINI-rfgg-vpp5-v4pm, RHSA-2026:7458, ROOT-OS-DEBIAN-11-CVE-2025-68972, ROOT-OS-DEBIAN-13-CVE-2025-68972, ROOT-OS-UBUNTU-2204-CVE-2025-68972

## What is CVE-2025-68972?

CVE-2025-68972 is a medium-severity vulnerability in GnuPG, published on 27 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2025-68972?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gnupg2` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-dirmngr` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-g13` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-gpg-agent` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-gpgconf` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-keyboxd` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-scdaemon` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-smime` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-utils` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-verify` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |
| `gnupg2-wks` | Red Hat:hummingbird:1 | All versions | 0:2.4.9-5.1.hum1 |

Products: Gnupg Gnupg.

## How do I fix CVE-2025-68972?

Upgrade to a fixed version.

## Is CVE-2025-68972 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68972 exists.

## Other vulnerabilities in GnuPG

- [CVE-2022-3515](https://insights.sbomify.com/CVE-2022-3515/): Integer overflow in libksba (critical 9.8)
- [CVE-2008-1530](https://insights.sbomify.com/CVE-2008-1530/): Memory corruption in n/a (critical 9.3)
- [CVE-2026-24882](https://insights.sbomify.com/CVE-2026-24882/): Memory corruption in GnuPG (high 8.4)
- [CVE-2026-24881](https://insights.sbomify.com/CVE-2026-24881/): Memory corruption in GnuPG (high 8.1)
- [CVE-2025-68973](https://insights.sbomify.com/CVE-2025-68973/): Memory corruption in GnuPG (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68972 and fix it if it is affected.

What it is: CVE-2025-68972 is a medium-severity vulnerability in GnuPG, published on 27 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68972 exists.

Affected product: GnuPG. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68972/ (Markdown: https://insights.sbomify.com/CVE-2025-68972/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68972
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68972
- OSV: https://osv.dev/vulnerability/CVE-2025-68972

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68972/
Summaries are generated and may contain mistakes; the official description above is the record.