On this page (7 sections)

On November 20, 2026, the Debian security team published advisory DSA-6646-1 for gpgme1.0, the package that provides GPGME, a library that makes it easier for applications to use GnuPG. The advisory covers CVE-2026-129975, a flaw in how the library handles OpenPGP keys that contain a crafted, very long user ID.

If you run Debian 13 (trixie) servers, especially ones that verify signatures, import public keys or run software that links against GPGME, you should check your package version and update. Only the Debian advisory is available so far, so some details, such as a severity score, are not yet known.

What happened

According to the Debian security advisory, researcher Johan Carlsson discovered that GPGME does not properly handle OpenPGP keys containing a crafted very long user ID. Debian says the consequences could include information disclosure, denial of service and potentially the execution of arbitrary code.

The wording matters. Debian lists three possible outcomes, and says code execution is only a potential result. The advisory does not say which of these is realistic in practice, does not describe the conditions required, and does not say whether anyone is exploiting the problem. Treat those points as unconfirmed until more information is published.

Why a long user ID can be a problem

An OpenPGP key carries one or more user IDs, which are free-text labels such as a name and email address. Anyone can create a key with whatever user ID they like, and software often reads those fields when it imports, lists or verifies keys. If a library assumes a field will be a reasonable size and does not enforce a limit correctly, an oversized value can lead to memory handling errors. That general class of bug is how a malformed input can turn into a crash, leaked memory contents or, in the worst case, code execution.

The advisory does not publish the specific root cause, so this is background on the weakness class rather than a description of this exact bug. What the advisory does confirm is that the trigger is a key with a crafted, very long user ID, which means the input is attacker-controlled data that an application would have to process.

Who is realistically exposed

GPGME is a library, so the risk depends on which programs use it and what keys they handle. Systems most worth checking include:

  • Servers that import or verify OpenPGP keys from outside sources, such as mail gateways, package or release signing workflows and CI systems.
  • Desktop or server applications that link against GPGME and parse keys supplied by users or downloaded from key servers.
  • Hosts where automated jobs fetch public keys and process them without review.

A machine that has the library installed but never touches untrusted keys is less likely to be affected, but it is still worth updating because the fix is a routine package upgrade.

How to check your exposure

The advisory states the fix for trixie, so the main question is whether the installed packages built from the gpgme1.0 source are older than 1.24.2-3+deb13u1. Binary package names vary, so start by listing what is installed. This read-only command lists installed packages whose name contains gpgme, with their versions. Run it on each Debian host and compare the version column against the fixed version.

List installed GPGME packages and versions (Debian)Shell
dpkg -l | grep -i gpgme

To see whether your configured repositories already offer the fixed build, take a package name from the listing above and run this read-only query, replacing PACKAGE_NAME with that exact name. Look at the Installed and Candidate lines; Candidate should be 1.24.2-3+deb13u1 or newer on trixie.

Show installed and candidate versions of a package (Debian)Shell
apt-cache policy PACKAGE_NAME
For the authoritative status per release, Debian points to the gpgme1.0 security tracker page at https://security-tracker.debian.org/tracker/gpgme1.0.

What to do now

Debian recommends upgrading your gpgme1.0 packages. The advisory only names a fixed version for trixie. It does not list fixed versions for other Debian releases, so check the security tracker for the status of any older release you run.

Caution. Upgrading a shared library does not change programs that are already running. Long-running services that loaded the old library keep using it until they are restarted. Schedule restarts of affected services in a maintenance window rather than restarting production services blindly.
  1. Inventory Debian 13 (trixie) hosts and identify which run applications that use GPGME.
  2. Run the dpkg listing above and note any host with a GPGME package older than 1.24.2-3+deb13u1.
  3. Refresh package lists and upgrade the GPGME packages on each affected host.
  4. Restart services that use the library, or reboot the host, so running processes load the fixed version.
  5. Check the Debian security tracker for older releases you still operate and plan their updates.
  6. Review where your systems fetch OpenPGP keys from and avoid processing keys from untrusted sources automatically.

This command refreshes the package index and upgrades all installed packages that have newer versions available, which includes the fixed GPGME packages once your repositories offer them. Run it as root or with sudo, then confirm the new versions with the dpkg listing.

Refresh package lists and apply available upgrades (Debian)Shell
sudo apt update && sudo apt upgrade

If you prefer to upgrade only GPGME, use the exact package names you found in the dpkg listing instead of a guessed name.

Upgrade only specific packages (Debian, replace with names from the dpkg listing)Shell
sudo apt update && sudo apt install --only-upgrade PACKAGE_NAME
Tip. If you manage many servers, a full upgrade through your normal patch process is simpler than upgrading single packages, and it picks up other pending security fixes.

Detection and monitoring afterwards

The advisory contains no indicators of compromise and no exploitation reports, so there is nothing specific to hunt for. General hygiene still applies after patching: watch for unexpected crashes of services that handle OpenPGP keys, since denial of service is one of the listed outcomes, and keep an eye on logs of key import jobs for failures or unusually large inputs.

Keep subscribing to the debian-security-announce list or your distribution's security feed so that follow-up information on this CVE, such as a severity score or exploitation reports, reaches you quickly. For the web-facing side of your estate, Webforta Scan can check the sites you verify, and the security guides hub covers patching habits. Outside-in checks cannot see which library versions run on your servers, so package-level checks like the ones above remain necessary.

What we do not know yet

  • No CVSS score or severity rating appears in the advisory.
  • No details on exploitation conditions, or whether code execution is practical, have been published in the material available.
  • No information on whether the flaw is being exploited.
  • Only one publisher, Debian, covers this so far, so treat details as preliminary.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6646-1] gpgme1.0 security updatelists.debian.org ·
  • Debian
  • GPGME
  • OpenPGP
  • CVE-2026-129975
  • Patch management