Today's cybersecurity headlines are brought to you by ThreatPerspective


Ethical Hacking News

GnuPG Warns of Critical GPGME Flaw, Leaving App Data Vulnerable to Malicious OpenPGP Keys




GnuPG has issued a critical warning about a vulnerability in its GPGME library, which could expose sensitive data stored in affected applications to malicious OpenPGP keys. The vulnerability, tracked as CVE-2026-129975, is a double-free error that can be triggered by a malicious OpenPGP key with an unusually long user ID. Users who rely on GnuPG for secure communication and data protection should update to the latest version of the GPGME library and apply any available patches to prevent potential exploitation of this critical vulnerability.

  • There is a critical vulnerability in the GPGME library, tracked as CVE-2026-129975, which can expose sensitive data to malicious OpenPGP keys.
  • The vulnerability is a double-free error, which can result in data corruption or exposure.
  • Many software applications, including mail clients and Samba, are vulnerable to this critical flaw due to their use of the GPGME library.
  • Users who rely on GnuPG for secure communication and data protection should update to version 2.3.1 or apply available patches to prevent exploitation.
  • Users should also be cautious when using OpenPGP keys and ensure they are properly validated and trusted.



  • GnuPG, a widely used open-source implementation of the OpenPGP standard, has recently issued a critical warning about a vulnerability in its GPGME library, which could expose sensitive data stored in affected applications to malicious OpenPGP keys. This vulnerability, tracked as CVE-2026-129975, has significant implications for users who rely on GnuPG for secure communication and data protection.

    The vulnerability is a double-free error, which occurs when the same memory is released twice, resulting in data corruption or exposure. This bug was discovered by Johan Carlsson, a researcher, and reported to the GnuPG project by GitLab. The project has since released fixed versions of the GPGME library, specifically version 2.3.1, to address this issue.

    The GPGME library is used by a wide range of applications, including most mail clients, many XMPP clients, Samba, and GnuPG Desktop, to work with GnuPG. As a result, many software applications are vulnerable to this critical flaw, which could allow an attacker to steal sensitive data, such as encryption keys or other confidential information, from affected applications.

    The vulnerability is particularly concerning because it can be triggered by a malicious OpenPGP key with an unusually long user ID. When such a key is used to sign data sent to an application, it can cause the GPGME library to free the same memory twice, resulting in data corruption or exposure. This bug can be exploited by an attacker who has access to a malicious OpenPGP key, allowing them to intercept and steal sensitive data.

    The GnuPG project has acknowledged that no attacks exploiting this flaw have been reported, but they have noted that remote code execution cannot be ruled out. This means that even if no malicious attacks have been detected, there is still a risk that an attacker could use this vulnerability to launch a remote code execution attack, which could potentially allow them to gain full control over an affected application.

    The GnuPG project has provided guidance on how to update to the fixed library version, specifically version 2.3.1, which is now available for download from the project's official website. In addition, the project has released a patch for older versions of the GPGME library, as well as a fixed release for the legacy branch, version 1.24.4.

    However, the project has noted that updating to the fixed library version may not be possible for all software applications, particularly those that are bundled or statically linked into the program. In such cases, the application's developers will need to rebuild their application with the updated library to ensure that the vulnerability is patched.

    The GnuPG project's warning about this critical vulnerability serves as a reminder of the importance of keeping software up to date and vigilant in the face of emerging security threats. As with any vulnerability, it is essential to stay informed about the latest developments and to take prompt action to update affected software to prevent potential exploitation.

    In light of this critical warning, users who rely on GnuPG for secure communication and data protection should take the following steps:

    * Update to the latest version of the GPGME library, specifically version 2.3.1, as soon as possible.
    * Apply the patch for older versions of the GPGME library, if available.
    * Consult with the application's developers to determine if they will be rebuilding their application with the updated library.
    * Be cautious when using OpenPGP keys and ensure that they are properly validated and trusted.

    By taking these steps, users can help prevent potential exploitation of this critical vulnerability and ensure the security and integrity of their data.



    Related Information:
  • https://www.ethicalhackingnews.com/articles/GnuPG-Warns-of-Critical-GPGME-Flaw-Leaving-App-Data-Vulnerable-to-Malicious-OpenPGP-Keys-ehn.shtml

  • https://thehackernews.com/2026/11/gnupg-warns-critical-gpgme-flaw-could.html

  • https://nvd.nist.gov/vuln/detail/CVE-2026-129975

  • https://www.cvedetails.com/cve/CVE-2026-129975/


  • Published: Sat Nov 21 05:55:59 2026 by llama3.2 3B Q4_K_M













    © Ethical Hacking News . All rights reserved.

    Privacy | Terms of Use | Contact Us