How We Could Have Backdoored Bash (Hacktron blog)
Comments on “How We Could Have Backdoored Bash (Hacktron blog)”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Hacktron says a shell injection in the email field of Savane, the software behind GNU Savannah, let any registered user run code on the server. It reports escalating to superuser, confirming it could add an SSH key with push access to Bash's upstream repository, and reaching root and a backup server through an unpatched kernel. After a May 11, 2026 report, it found 25 more flaws; the FSF fixed all 26. The account is Hacktron's own. It shows how one input-validation flaw can reach source repositories.
Why it ranked
No. 19 of 59 with a score of 0.67. The panel rated it highest on new information (0.85) and reader interest (0.78), lowest on substantiated (0.49). The judges disagreed most on substantiated (spread 0.43), so the story is marked contested. Placed No. 19, No. 11 by score alone: the eighth Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Strong security write-up of a real supply-chain compromise path against Bash/GNU infrastructure; substantive technical chain but excerpt is short and claims are only partly detailed.
- AI judgeJudge 3gpt-5.6-luna
- A concrete forge compromise enabled maintainer impersonation and upstream Bash push access, making this highly relevant to software supply-chain security. The excerpt provides technical exploit details and disclosure timing, though not a full reproducible report.
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.67total under rubric v2.3Contestedjudges differ by 0.43 on substantiated
- Significance0.70
- Reader interest0.78
- Audience breadth0.73
- Practical relevance0.68
- Substantiated0.49
- Technical depth0.66
- New information0.85
- Counts against: Promotional0.05
- Counts against: Overclaim0.32
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.65 | 0.62 | 0.82 | 0.70 | 0.20 | +0.24 | +0.167 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.58 | 0.82 | 0.94 | 0.78 | 0.36 | +0.26 | +0.203 |
| Audience breadthHow many people who build technology does it concern? | 0.70 | 0.70 | 0.78 | 0.73 | 0.08 | +0.13 | +0.094 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.60 | 0.60 | 0.83 | 0.68 | 0.23 | +0.22 | +0.149 |
| 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.29 | 0.45 | 0.72 | 0.49 | 0.43 , above the contested threshold | +0.05 | +0.024 |
| Technical depthHow technically substantive is it? | 0.67 | 0.55 | 0.76 | 0.66 | 0.21 | +0.05 | +0.033 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.86 | 0.70 | 0.98 | 0.85 | 0.28 | +0.05 | +0.042 |
| 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.08 | 0.05 | 0.02 | 0.05 | 0.06 | −0.19 | −0.010 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.49 | 0.30 | 0.18 | 0.32 | 0.31 | −0.11 | −0.036 |
| Sum of contributions | +0.668 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.668 | ||||||
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-01/19/"><img src="https://rubric.hrih.si/badge/2026-11-01/19.svg" alt="Ranked #19 on Rubric, 1 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 5 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenCausal conclusion
An email address containing a shell command such as `touch${IFS}/tmp/savane-rce-proof`@attacker.example gave any registered user code execution on the GNU Savannah backend.
The article gives no link or citation for it.
The article says “an email address like `touch${IFS}/tmp/savane-rce-proof`@attacker.example gave any registered user code execution on its backend”
The source says No source to compare with.
No source givenNumber
Hacktron's researchers used the access to make their account a superuser, impersonate Bash's maintainer, and confirmed they could add an SSH key with push access to the upstream Bash repository.
The article gives no link or citation for it.
The article says “we made our account a superuser, impersonated Bash's maintainer, and confirmed we could add an SSH key with push access to the upstream Bash repository”
The source says No source to compare with.
No source givenCausal conclusion
An unpatched kernel gave the researchers root access and access to a GNU backup server.
The article gives no link or citation for it.
The article says “An unpatched kernel gave us root access and access to a GNU backup server”
The source says No source to compare with.
No source givenDate
Hacktron reported the vulnerability to the FSF on May 11, 2026.
The article gives no link or citation for it.
The article says “We reported it to the FSF on May 11, 2026”
The source says No source to compare with.
No source givenGeneralization
The group compromised the GNU Savannah forge and could have pushed malware into any of the projects hosted there.
The article gives no link or citation for it.
The article says “the group was able to compromise the GNU Savannah forge and could have pushed malware into any of the projects hosted there”
The source says No source to compare with.
Also covered by
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 1 Nov 2026, 05:47 UTC. It played no part in the ranking.