Debian Fixes GPGME Handling of Crafted OpenPGP User IDs

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

On Debian 13 (trixie), update gpgme1.0 to 1.24.2-3+deb13u1 or the supported superseding package and validate its dependent applications.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Debian release, package versions, application owners, deployment images and the processes that load gpgme1.0. Identify applications using Debian GPGME and workflows importing or inspecting keys from external sources. Install the corrected Debian security packages for trixie through the supported repository and rebuild application images that include the vulnerable package. Restart affected consumers as appropriate, verify legitimate key import and signature workflows, and retain package and validation records.

Open the authoritative advisory

Last verified: 2026-11-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopegpgme1.0 on Debian 13 (trixie)
AdvisoryDSA-6646-1
CVECVE-2026-129975
Authoritative release date2026-11-20T21:36:59Z — timestamp in the Debian security-announcement message.
Authority revision dateNo separate material revision is stated for this release.
Affected versionsDebian 13 (trixie) gpgme1.0 packages before 1.24.2-3+deb13u1. The advisory does not establish an affected range for other distributions.
Fixed versiongpgme1.0 1.24.2-3+deb13u1 for Debian 13 (trixie).
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not state that these vulnerabilities are being exploited in the wild.; no exploitation claim is inferred.

What Changed

GPGME mishandles OpenPGP keys with a crafted very long user ID, potentially causing information disclosure, denial of service or arbitrary code execution.

What To Validate Now

  1. Inventory. Record Debian release, package versions, application owners, deployment images and the processes that load gpgme1.0.
  2. Establish applicability. Identify applications using Debian GPGME and workflows importing or inspecting keys from external sources.
  3. Remediate. Install the corrected Debian security packages for trixie through the supported repository and rebuild application images that include the vulnerable package.
  4. Validate. Restart affected consumers as appropriate, verify legitimate key import and signature workflows, and retain package and validation records.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

The Debian bulletin supplies neither a CVSS score nor an exploitation statement. Its package fix does not establish that separately bundled copies were updated.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.