CVE-2025-30258: Medium severity gnupg GnuPG vulnerability

Published Mar 19, 2025
·
Updated

In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."

Affected Software

7 affected componentsFixes available
gnupg GnuPG<2.5.5
debian/gnupg2<=2.2.27-2+deb11u2, <=2.2.40-1.1
2.2.46-6
gnupg GnuPG<2.4.8
gnupg GnuPG>=2.5.0<2.5.5
Microsoft cbl2 gnupg2 2.4.0-2
Microsoft azl3 gnupg2 2.4.7-1
Microsoft azl3 gnupg2 2.4.9-2<2.4.8-1
2.4.8-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/gnupg2 to a version that resolves this vulnerability.

    Fixed in 2.2.46-6
  2. Upgrade

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

    Fixed in 2.4.8-1
  3. Upgrade

    Upgrade GnuPG to a version that resolves this vulnerability.

    Fixed in 2.5.5

Event History

Mar 19, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
Affected Software
Apr 7, 2025
Data Sourced
via Ubuntu·05:27 PM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·03:09 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·03:09 AM
Affected Software
Updated
via Microsoft·10:09 AM
DescriptionSeverity
Updated
via Microsoft·10:09 AM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-30258?

CVE-2025-30258 is classified as a verification denial-of-service vulnerability, which can severely impact the user's ability to verify signatures.

2

How do I fix CVE-2025-30258?

To fix CVE-2025-30258, upgrade to GnuPG version 2.5.5 or later, which addresses this vulnerability.

3

What versions of GnuPG are affected by CVE-2025-30258?

GnuPG versions prior to 2.5.5 are affected by CVE-2025-30258.

4

What are the consequences of CVE-2025-30258?

The consequence of CVE-2025-30258 is that it can lead to a loss of the ability to verify signatures from certain signing keys.

5

Is there a workaround for CVE-2025-30258?

There are no known workarounds for CVE-2025-30258 other than upgrading to a non-vulnerable version.

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