Git 2.56.1 fixes six vulnerabilities, including RCE on recursive clone
Comments on “Git 2.56.1 fixes six vulnerabilities, including RCE on recursive clone”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Git 2.56.1 fixes six vulnerabilities, with backports down to 2.50.2. GitHub's Elijah Newren describes the most serious as an integer truncation in index path handling that can allow code execution during a recursive clone of a malicious repository. The others cover path traversal via a server's advertised HEAD, memory corruption in signature stripping and large merges, a binary-patch out-of-bounds read, and fast-import file access. Update bundled copies and services that clone or merge untrusted content. Two advisories and the Enterprise Server version numbers could not be verified.
Why it ranked
No. 1 of 143 with a score of 0.80. The panel rated it highest on practical relevance (0.94) and new information (0.89), lowest on significance (0.70).
- AI judgeJudge 2claude-haiku-5-5
- Security release of Git, a foundational developer tool, with six CVEs including RCE and memory corruption, clear advisories and actionable upgrade guidance. Strongly relevant to builders.
- AI judgeJudge 3gpt-5.6-luna
- A primary Git security release details six vulnerabilities, including recursive-clone RCE, affected workflows, mitigations, and version updates. It is broadly actionable for developers, CI systems, hosting services, and anyone processing untrusted repositories.
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.80total under rubric v2.3
- Significance0.70
- Reader interest0.84
- Audience breadth0.83
- Practical relevance0.94
- Substantiated0.87
- Technical depth0.77
- New information0.89
- Counts against: Promotional0.09
- Counts against: Overclaim0.11
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.74 | 0.55 | 0.82 | 0.70 | 0.27 | +0.24 | +0.169 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.83 | 0.80 | 0.90 | 0.84 | 0.10 | +0.26 | +0.219 |
| Audience breadthHow many people who build technology does it concern? | 0.86 | 0.80 | 0.82 | 0.83 | 0.06 | +0.13 | +0.108 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.98 | 0.90 | 0.93 | 0.94 | 0.08 | +0.22 | +0.206 |
| 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.81 | 0.85 | 0.96 | 0.87 | 0.15 | +0.05 | +0.044 |
| Technical depthHow technically substantive is it? | 0.80 | 0.70 | 0.82 | 0.77 | 0.12 | +0.05 | +0.039 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.80 | 0.99 | 0.89 | 0.19 | +0.05 | +0.045 |
| 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.09 | 0.10 | 0.08 | 0.09 | 0.02 | −0.19 | −0.017 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.19 | 0.10 | 0.03 | 0.11 | 0.16 | −0.11 | −0.012 |
| Sum of contributions | +0.800 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.800 | ||||||
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-11/1/"><img src="https://rubric.hrih.si/badge/2026-11-11/1.svg" alt="Ranked #1 on Rubric, 11 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 5 matches source · 1 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
Git 2.56.1 addresses six security vulnerabilities, with backports to Git 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, and 2.50.2.
The cited source says the same thing.
The article says “The fixes are included in Git 2.56.1, with backports to Git 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, and 2.50.2”
The source says “This release merges up the fix that appears in v2.50.2, v2.51.3, v2.52.1, v2.53.1, v2.54.1 and v2.55.1 to address CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467, CVE-2026-114469”
Source cited by the article: github.com/git/git/blob/v2.56.1/Documentation/RelNotes/2.56.1.adoc
Couldn’t checkCausal conclusion
An integer truncation in Git's index handling lets an extremely long path pass validation under one name and be written under a shorter name, which can enable replacing a submodule's .git file with a symlink and executing attacker-controlled code during a recursive clone (CVE-2026-111760).
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “an integer truncation in Git’s index handling can cause an extremely long path to pass validation under one name and then be written using a shorter name”
The source says No passage could be compared.
Source cited by the article: github.com/git/git/security/advisories/GHSA-vp2w-7xxj-jvxr
Matches sourceCausal conclusion
When cloning an empty repository over protocol v2, Git did not validate the HEAD symref target advertised by the server, so with the files reference backend a later branch update can write outside the intended reference directory (CVE-2026-113408).
The cited source says the same thing.
The article says “A malicious server can supply a name containing path-traversal components. With the files reference backend, a later operation that updates the branch can write outside the intended reference directory”
The source says “It is possible for a server to advertise an unborn `HEAD` that contains path-traversal characters (e.g., `refs/heads/../../../TARGET`). With the files ref backend that can lead to ref-updating actions to write…”
Source cited by the article: gitlab.com/gitlab-org/git/-/work_items/809
Matches sourceCausal conclusion
Git assumed at most two signatures when stripping GPG signatures, so a message with more than two signatures can cause a write past the end of a fixed-size stack array, triggered by merging such a tag (CVE-2026-114467).
The cited source says the same thing.
The article says “A specially crafted message containing more than two signatures can cause Git to write past the end of a fixed-size stack array”
The source says “When Git strips the GPG signatures from a commit message, it only accounts for two signatures. A commit message containing more than two signatures therefore causes a stack memory corruption”
Source cited by the article: gitlab.com/gitlab-org/git/-/work_items/810
Matches sourceCausal conclusion
Git rejects patches larger than approximately 1 GiB, but a small compressed binary patch can expand beyond that limit, bypass the check and cause an out-of-bounds read that crashes Git (CVE-2026-114469).
The cited source says the same thing.
The article says “A crafted patch can bypass the input-size check and cause an out-of-bounds read, crashing Git”
The source says “A binary patch that inflates to a very large size therefore slipped past the check and crashed Git with an out-of-bounds read”
Source cited by the article: gitlab.com/gitlab-org/git/-/work_items/811
Matches sourceCausal conclusion
The merge size calculation can overflow on very large results, including with many conflicts combined with a large conflict-marker-size attribute, causing a too-small buffer allocation and heap corruption (CVE-2026-105437).
The cited source says the same thing.
The article says “The overflow can cause Git to allocate a buffer that is too small, then write outside it, corrupting heap memory”
The source says “So a small file with a huge marker size and many separate conflicts can push the total past 4 GiB. The `int` then wraps to a small value”
Source cited by the article: gitlab.com/gitlab-org/git/-/work_items/814
Couldn’t checkCausal conclusion
The rewrite-submodules-from and rewrite-submodules-to features can read arbitrary files, and export-pack-edges can create files or append data to existing files; these are now rejected in untrusted fast-import streams unless --allow-unsafe-features is set.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The rewrite-submodules-from and rewrite-submodules-to features can read arbitrary files, potentially exposing their contents through error messages. The export-pack-edges option can create files or append data to existing files”
The source says No passage could be compared.
Source cited by the article: gitlab.com/gitlab-org/git/-/work_items/812
No source givenVersion
GitHub Enterprise Server updates fixing these vulnerabilities are available in versions 3.19.15, 3.20.11, 3.21.9, and 3.22.4.
The article gives no link or citation for it.
The article says “Updates for GitHub Enterprise Server are available in versions 3.19.15, 3.20.11, 3.21.9, and 3.22.4”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 5 pts, not on front page
Recorded for context only, checked 11 Nov 2026, 05:47 UTC. It played no part in the ranking.