CVE-2025-68972: Medium severity gnupg GnuPG vulnerability

Published Dec 27, 2025
·
Updated

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.

Affected Software

4 affected componentsFixes available
gnupg GnuPG<=2.4.8
Microsoft azl3 gnupg2 2.4.7-1
gnupg GnuPG<=2.4.8
Microsoft azl3 gnupg2 2.4.7-1<2.4.9-1
2.4.9-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.4.9-1

Event History

Dec 27, 2025
CVE Published
via MITRE·10:52 PM
Data Sourced
via MITRE·10:52 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software
Dec 29, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·09:01 AM
DescriptionSeverity
Updated
via Microsoft·09:01 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-68972?

CVE-2025-68972 is classified as a high-severity vulnerability due to its potential for misuse in signature verification.

2

How do I fix CVE-2025-68972?

To fix CVE-2025-68972, users should upgrade GnuPG to version 2.4.9 or later.

3

What software is affected by CVE-2025-68972?

CVE-2025-68972 affects GnuPG versions up to and including 2.4.8.

4

What type of attack does CVE-2025-68972 enable?

CVE-2025-68972 enables an adversary to manipulate signed messages to succeed in signature verification despite unauthorized modifications.

5

What should I do if I cannot upgrade due to compatibility issues related to CVE-2025-68972?

If upgrading is not possible, it's recommended to implement strict validation checks on all signed messages.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203