News
A long OpenPGP user ID can expose app data through GPGME.
GnuPG warned that a malicious OpenPGP key with an unusually long user ID can trigger a double-free in GPGME, the library programs use to talk to GnuPG. The bug, CVE-2026-129975, could be used to steal data from affected applications, and remote code execution cannot be ruled out. The fixed library is GPGME 2.3.1.

Impact
- What was impacted
- GPGME before version 2.3.0, whether the program loads it as a shared library, a Windows DLL, or a copy linked into the program. CVE-2026-129975 is a double-free in the routines that read status lines and key listings coming back from GnuPG. When the input is long, those routines move the data to a larger buffer but record the new address only if they finish without an error. An error in between leaves a pointer to memory that was already freed, and cleanup frees it again. The project's example is a malicious OpenPGP key with an unusually long user ID. It also points to signed data sent to an application. The advisory does not say which programs pass that material to the library without a person importing the key.
- Who was impacted
- Anyone whose software uses GPGME before 2.3.0. The project names most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages. It has not reported any attacks using the flaw. GPGMEPP and GPGMEQT do not need an update.
- What you need to do
- Install GPGME 2.3.1 for a shared library or DLL. A public 2.3.0 was never released. On Windows, Gpg4win 5.1.2 bundles the fixed library. Its release notes call the issue severe and say to update as soon as possible. If a system cannot move to 2.3.1, the advisory carries a patch, and the legacy branch has its own fixed release, 1.24.4. The notes on that legacy release say the project cannot guarantee the branch will receive every security patch. Updating the system library does not fix a copy that is bundled or linked into an application, so those applications need their own rebuilt releases. There is no interim workaround. Do not import a crafted key to test whether a program is vulnerable.
A malicious OpenPGP key with an unusually long user ID can trigger a critical memory bug in GPGME, the library programs use to work with GnuPG. The GnuPG project warned yesterday that the flaw could be used to steal data from affected applications, and it has released fixed versions. The bug is CVE-2026-129975. It affects software that uses GPGME before 2.3.0, including a shared library, a Windows DLL, or a copy built into the program.
The project names most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages as examples. It has not reported attacks using the flaw. It also says remote code execution cannot be ruled out. One path it describes is signed data sent to an application. The advisory does not say which programs hand that material to the library without a manual key import.
The bug is a double-free: the same memory is released twice. It sits in the two routines that read status lines and key listings coming back from GnuPG. When the input runs long, the routines move the data into a larger buffer, but they record the new address only if they finish without an error. An error in between leaves a pointer to memory that was already freed, and cleanup frees it a second time. Johan Carlsson found the flaw. GitLab reported it to the project last week. Disclosure had been set for November 25 and was moved up because a separate Ruby flaw forced GitLab to update earlier.
The fixed library is GPGME 2.3.1, released this week. Version 2.3.0 was never publicly available. A shared library or DLL should be updated to 2.3.1. On Windows, Gpg4win 5.1.2 includes that library, and its notes call the issue severe. Systems that cannot move to 2.3.1 can use the patch in the advisory, or the legacy release 1.24.4. The project says it cannot guarantee that legacy branch will get every later security fix.
Copies that are bundled or linked into an application stay vulnerable after the system library is updated. Those applications need their own rebuilt releases. GPGMEPP and GPGMEQT do not need an update. The advisory gives no workaround for software that cannot be updated yet. Do not test the bug with a crafted key.
For your AI agent
Agent instructions — copy paste to Claude
You are helping me respond to CVE-2026-129975, a double-free in GPGME before version 2.3.0. A malicious OpenPGP key with an unusually long user ID can trigger it, and GnuPG says the flaw could be used to steal data from affected applications. Remote code execution cannot be ruled out. Do not write or import a crafted key, a proof of concept, or any test that feeds long status or key-listing data into GPGME. Ask before installing a package, rebuilding an application, or removing a program. Facts from the report: - The bug affects all software that uses GPGME before 2.3.0, whether the library is a shared library, a Windows DLL, or statically linked into the program. Examples the project gives are most mail clients, many XMPP clients, Samba, and its own Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop packages. Do not treat that list as complete, and do not invent other product names. - The project has not reported any attacks exploiting the flaw. - Its example of a path is signed data sent to an application. The advisory does not say which programs pass that material to the library without a manual key import. Do not guess a mail client or messenger is exposed just because it can verify mail. - The flaw is a double-free in read_status() and read_colon_line(), which read status lines and key listings from GnuPG. Long input is moved to a larger buffer, and the new address is recorded only if the routine finishes without errors. An error in between leaves a pointer to memory that was already freed, and cleanup frees it again. Do not turn that description into a crash input. - Johan Carlsson found the flaw. GitLab reported it last week. Disclosure had been set for November 25 and was moved up because the Ruby2Shell bug forced GitLab to update earlier. Do not treat Ruby2Shell as this CVE. - The fixed library is GPGME 2.3.1, released this week. Version 2.3.0 was never publicly available. Do not tell me to install 2.3.0. - Shared library or DLL: update to GPGME 2.3.1. Windows: Gpg4win 5.1.2 bundles the fixed library, and its release notes call the issue severe. Older systems that cannot move to 2.3.1: the advisory carries a patch, and the legacy branch has fixed release 1.24.4. The legacy notes say the project cannot guarantee that branch will see every security patch. Say that limit if I would stay on 1.24.4. - Bundled and statically linked copies are affected, and an update to the system shared library does not reach them. Those applications need their own rebuilt releases. - GPGMEPP and GPGMEQT need no update. Do not flag them. - There is no interim workaround. Do not invent one. Context: - What was impacted: applications that use GPGME before 2.3.0, including shared, DLL, and statically linked copies. - Who should care: operators of mail clients, XMPP clients, Samba, Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop that depend on that library, and anyone else who ships or installs GPGME. - What to do: install GPGME 2.3.1, or Gpg4win 5.1.2 on Windows. Use the advisory patch or legacy 1.24.4 only when 2.3.1 is not possible, and say the legacy branch may not get every later fix. Rebuild applications that carry their own copy. Do this in order. Ask before installing or rebuilding. Prefer read-only inventory first. Do not write or run an exploit or a proof of concept. 1. Inventory - Find GPGME copies I run: shared library, Windows DLL, and applications that link their own copy. Record the version if you can read it without changing the system. - A version below 2.3.0 is in the affected range this report describes. 2.3.1 is the fixed library. 2.3.0 was never public, so do not treat a claimed 2.3.0 as the fix. If you cannot read a version, say so. Do not mark an unknown version as safe. - Record Gpg4win, GnuPG Desktop, and GnuPG VS-Desktop if they are installed. Gpg4win 5.1.2 is the Windows bundle named in this report. Do not invent a build number for the Desktop packages. - Note GPGMEPP and GPGMEQT only to say they do not need an update. - Do not import a key or send signed data to test the bug. 2. Contain - There is no workaround in the advisory. Do not propose one. - If an affected library is in use and I cannot update it yet, say that plainly. Ask before stopping a service. 3. Remediate - Plan GPGME 2.3.1 for a shared library or DLL, and Gpg4win 5.1.2 where that Windows bundle is what I run. Ask before installing. - If I cannot move to 2.3.1, the choices in this report are the advisory patch or legacy 1.24.4. Say that the project does not guarantee every later security patch on that legacy branch. - For a bundled or statically linked copy, say the system library update does not fix it. Ask before rebuilding or upgrading that application. 4. Verify - After an update I asked you to perform, read the version again. Claim it is fixed only when it is 2.3.1, Gpg4win 5.1.2, or 1.24.4 on the legacy branch, or when I show you a rebuilt application that contains the fix. - If I did not ask you to change anything, report the inventory only. 5. Report back - Which GPGME copies you found, their versions, which ones a system update would miss, what you changed, and that the project has not reported attacks using this flaw. Do not invent CVEs, package versions, or signs of a past intrusion. If a check needs access I have not given you, say what you need and stop.