GnuPG Security Advisory for Gpgme (T8557,CVE-2026-129975)
Comments on “GnuPG Security Advisory for Gpgme (T8557,CVE-2026-129975)”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
GnuPG released GPGME 2.3.1 to fix a double free that a crafted OpenPGP key with a very long user ID can trigger. Werner Koch's advisory says it could leak application data and that remote code execution can't be ruled out. The cause is a reallocated buffer pointer saved to the context only at function end, leaving a stale pointer on early return. Software using earlier versions, including statically linked builds, is affected. Rebuild or patch; Gpg4win 5.1.2 ships the fix. These details come only from the advisory.
Why it ranked
No. 11 of 118 with a score of 0.73. The panel rated it highest on substantiated (0.93) and new information (0.92), lowest on audience breadth (0.63). Placed No. 11, No. 6 by score alone: the fifth Security story of the day (−0.040). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Security advisory for widely used GPGME library with a double-free bug, including a concrete patch and affected-software list; primary source, technically specific, practically urgent for builders.
- AI judgeJudge 3gpt-5.6-luna
- A primary security advisory details a widespread GPGME double-free, affected applications, remediation, patch, and release artifacts. It is highly actionable and technically substantiated, though exploitability claims remain partly precautionary.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.73total under rubric v2.3
- Significance0.65
- Reader interest0.79
- Audience breadth0.63
- Practical relevance0.87
- Substantiated0.93
- Technical depth0.84
- New information0.92
- Counts against: Promotional0.04
- Counts against: Overclaim0.30
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.63 | 0.55 | 0.78 | 0.65 | 0.23 | +0.24 | +0.156 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.63 | 0.80 | 0.93 | 0.79 | 0.30 | +0.26 | +0.205 |
| Audience breadthHow many people who build technology does it concern? | 0.63 | 0.67 | 0.58 | 0.63 | 0.09 | +0.13 | +0.081 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.89 | 0.85 | 0.88 | 0.87 | 0.04 | +0.22 | +0.192 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.97 | 0.85 | 0.96 | 0.93 | 0.12 | +0.05 | +0.046 |
| Technical depthHow technically substantive is it? | 0.94 | 0.75 | 0.82 | 0.84 | 0.19 | +0.05 | +0.042 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.90 | 0.98 | 0.92 | 0.09 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.07 | 0.03 | 0.03 | 0.04 | 0.04 | −0.19 | −0.008 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.48 | 0.15 | 0.28 | 0.30 | 0.33 | −0.11 | −0.033 |
| Sum of contributions | +0.727 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.727 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-21/11/"><img src="https://rubric.hrih.si/badge/2026-11-21/11.svg" alt="Ranked #11 on Rubric, 21 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 5 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceVersion
GPGME version 2.3.1 fixes a critical security bug found in all prior versions.
The cited source says the same thing.
The article says “This version fixes a *critical security bug* found in all prior versions”
The source says “We have fixed this with gpgme 2.3.1 ( T8427 ) and provided the tarball and a patch to the reporter for further distribution to Linux distros”
Source cited by the article: static.dev.gnupg.org/T8557
Couldn’t checkCausal conclusion
A crafted OpenPGP key with a very long user id can trigger a double free in GPGME, which can be used to exfiltrate data from applications.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “By using an OpenPGP key containing a crafted very long user id it is possible to trigger a double free”
The source says No passage could be compared.
Source cited by the article: static.dev.gnupg.org/T8557
No source givenDate
The vulnerability was discovered by Johan Carlsson and GnuPG was informed by GitLab on 2026-11-12.
The article gives no link or citation for it.
The article says “This vulnerability was discovered by Johan Carlsson and we were informed by GitLab on 2026-11-12”
The source says No source to compare with.
No source givenCausal conclusion
Disclosure was moved from the planned 2026-11-25 to 2026-11-20 because GitLab had to update earlier due to the Ruby2Shell bug.
The article gives no link or citation for it.
The article says “due to the new Ruby2Shell bug GitLab had to update earlier and thus we also disclosed the GPGME bug on 2026-11-20”
The source says No source to compare with.
No source givenCausal conclusion
The root cause is that two internal functions reading status lines and key listings only assign the reallocated buffer back to the context at function end, leaving a stale pointer on early return and causing a double free.
The article gives no link or citation for it.
The article says “When reallocating the pointer to the new buffer is used by the function but it is only assigned back to the context object at the end of the function”
The source says No source to compare with.
No source givenGeneralization
All software using a GPGME version prior to 2.3.0, as shared library, DLL or statically linked, is affected.
The article gives no link or citation for it.
The article says “All software using a GPGME version prior to 2.3.0 either as shared libary, DLL, or statically linked is affected”
The source says No source to compare with.
Couldn’t checkVersion
Gpg4win version 5.1.2 has been released including the fixed GPGME.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “A new version of Gpg4win (5.1.2), our full featured Windows installer, including the fixed version of GPGME”
The source says No passage could be compared.
Source cited by the article: gpg4win.org
No source givenNumber
The patch states the fixed bug is 24 years old.
The article gives no link or citation for it.
The article says “This fixes a 24 years old bug introduced with”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 4 pts, not on front page
Recorded for context only, checked 21 Nov 2026, 05:47 UTC. It played no part in the ranking.