GPGME patches critical RCE vulnerability
The GnuPG project released GPGME 2.3.1 to patch a critical double-free vulnerability (CVE-2026-129975) triggered by crafted OpenPGP keys with oversized user IDs. The flaw impacts all versions prior to 2.3.0 across desktop apps and libraries, enabling data exfiltration and potential remote code execution.
While memory corruption in C crypto libraries is hardly novel, a potential RCE in GPGME is catastrophic because it sits quietly beneath tools developers trust implicitly.
- –A buffer reallocation bug in internal status-reading functions retains a stale pointer upon read errors, causing a double-free on context destruction.
- –GitLab's concurrent remediation of a Ruby2Shell vulnerability prompted an accelerated disclosure, shrinking the patching window for downstream maintainers.
- –The vulnerability reaches far into developer stacks, exposing Samba, Flatpak, Gpg4win, and automated commit-verification workflows.
- –Statically linked binaries and containerized tools will not benefit from system package updates and must be recompiled against GPGME 2.3.1.
- –Alongside the fix, the release quietly introduces constants for ML-KEM and ML-DSA, moving OpenPGP toward post-quantum readiness.
DISCOVERED
18m ago
2026-11-21
PUBLISHED
4h ago
2026-11-21
RELEVANCE
AUTHOR
gdgghhhhh