GitHub 'Verified' Commits Can Be Rewritten Into New Hashes Without Breaking Signatures
The article states the vulnerability exists but omits technical specifics about implementation conditions, reproducibility thresholds, tooling dependencies, or GitHub’s validation logic — presenting the effect without clarifying where responsibility lies or what mitigations exist.
View original on thehackernews.comOverview
Researchers demonstrated that GitHub's 'Verified' commit signature system can be bypassed by generating a second, distinct commit hash with identical content, authorship, and timestamp that still receives GitHub's 'Verified' badge, undermining the cryptographic integrity assumption behind signed commits.
TL;DR
- A new attack allows forging alternate Git commit hashes that retain identical content, author, date, and valid signatures.
- GitHub's 'Verified' badge persists despite hash mismatch, misleading reviewers into trusting cryptographic uniqueness.
- The finding exposes a gap between developer expectations of immutable commit identity and actual signature verification scope.
Key Stats
1
vulnerability class
Cryptographic hash collision via signature replay under deterministic timestamp and content constraints
Questions Answered
Keywords
Narrative Frame
accountability blur
Spin Score
40%
Emphasizes the observable outcome ('Verified' badge persists) while minimizing the precise mechanism (e.g., whether GitHub validates only signature + payload or also enforces hash binding), omitting whether this is a design choice, implementation bug, or protocol limitation.
What the story wants you to believe
That the 'Verified' badge’s meaning is fundamentally ambiguous because GitHub’s validation logic doesn’t enforce hash binding — making the problem systemic rather than operational.
What it makes harder to question
Whether this is a solvable engineering issue within GitHub’s control versus an unavoidable consequence of Git’s design or broader ecosystem assumptions.
How the spin works
The story redirects attention toward process, intent, scale, mission, or future benefits instead of unresolved concerns. Watch for loaded terms such as one-of-a-kind name, everything a reviewer would check matches, that matters. The distribution reads as editorial reporting. A pressure point: GitHub’s documented signature verification policy.
Who Benefits If This Frame Spreads
Research authors
Credibility and citation traction in security and DevOps communities
Framing the finding as a fundamental misconception rather than a patchable bug elevates its conceptual significance and broadens relevance beyond GitHub-specific remediation.
The Frame
Technical revelation exposing an industry-wide misconception about cryptographic guarantees.
Missing Context
- GitHub’s documented signature verification policy
- Whether GPG/SSH key formats or Git version affect exploit feasibility
- Whether this affects merge commits, tags, or only single commits
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
The article frames the issue as revealing a widespread misconception — not a GitHub failure — so readers focus on conceptual limits of cryptographic trust rather than accountability for platform safeguards.
- Claim
Given any signed commit
Given any signed commit, someone without the signing key can mint a second commit with the same files, author, and date, and a valid signature, GitHub still stamps 'Verified.'
- Frame
Key details stay obscured
Technical revelation exposing an industry-wide misconception about cryptographic guarantees.
- Beneficiary
Credibility and citation traction in security and DevOps communities
Research authors — Credibility and citation traction in security and DevOps communities
- Gap
GitHub’s documented signature verification policy
- AI Risk
AI may repeat the headline as fact
GitHub's 'Verified' commits can be forged with different hashes while retaining the badge, breaking trust in signed code.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| Given any signed commit, someone without the signing key can mint a second commit with the same files, author, and date, and a valid signature, GitHub still stamps 'Verified.' | Descriptive assertion of capability and observed behavior | Claim Present in Source | High | Proof-of-concept code or repository link; Tested Git version and signing method; GitHub API response logs showing signature acceptance for divergent hashes |
Given any signed commit, someone without the signing key can mint a second commit with the same files, author, and date, and a valid signature, GitHub still stamps 'Verified.'
evidence: Descriptive assertion of capability and observed behavior
"Given any signed commit, someone without the signing key can mint a second commit with the same files, author, and date, and a valid signature, GitHub still stamps 'Verified.'"
Evidence Gaps
- Proof-of-concept code or repository link
- Tested Git version and signing method
- GitHub API response logs showing signature acceptance for divergent hashes
Fact Check Signals
0 of 1 claim matched · confidence: low · checked July 9, 2026
Given any signed commit, someone without the signing key can mint a second commit with the same files, author, and date, and a valid signature, GitHub still stamps 'Verified.'
Language Heatmap
Loaded terms that carry the frame beyond the facts.
GitHub 'Verified' Commits Can Be Rewritten Into New Hashes Without Breaking Signatures
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
The Hacker News · Media
Counter-Frames
Brand Frame
Technical revelation exposing an industry-wide misconception about cryptographic guarantees.
Media / Reader Counter-Frame
Portraying it as a 'GitHub bug' rather than a consequence of Git’s signature model and GitHub’s validation scope.
Regulatory Counter-Frame
Highlighting inadequate transparency in platform security documentation and lack of user-facing warnings about hash non-uniqueness in signed contexts.
AI Summary Frame
Omitting the narrow preconditions (deterministic timestamps, identical tree/parent/author metadata) and overstating exploit practicality.
Missing Voices
Questions Not Answered
- Which specific Git versions or signing tools were tested?
- Has GitHub acknowledged or patched this behavior?
- What percentage of 'Verified' commits in public repos are vulnerable to this technique?
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"GitHub's 'Verified' commits can be forged with different hashes while retaining the badge, breaking trust in signed code."
Concern: AI may drop the nuance that this requires identical author/date/content and doesn’t enable arbitrary tampering — conflating it with full signature spoofing or private-key compromise.
-
Published
Jul 8, 2026
-
Ingested
Jul 8, 2026
-
SpinGraph Created
Jul 9, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_github_verified_commits_can_be_rewritten_into_ne
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
More from The Hacker News
View all →- FCC Blocks New Foreign-Produced Robots and Power Inverters Over Cyber Risks
- Russian Hackers Exploit Microsoft OWA Flaw to Keep Mailbox Access After Credential Rotation
- Hackers Exploit AnySign4PC via Hacked Korean Sites to Install Backdoors Without Prompts
- Cisco FMC Zero-Day Actively Exploited, Static Credentials Could Expose Sensitive Data
- Critical Rails Flaw Could Let Unauthenticated Attackers Read Server Files via Image Uploads
- 73% of Organizations Say They Are Not Fully Ready for a Major Cyberattack
Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO