GitHub ‘Verified’ Commits Can Be Rewritten Into New Hashes Without Breaking Signatures

A Critical GitHub Security Flaw Exposes Verified Commits to Rewrite Attacks

GitHub, one of the world’s most popular code repositories, has disclosed a security vulnerability that allows hackers to rewrite verified commits without breaking digital signatures. This flaw, discovered by researchers at the University of California, Berkeley, affects millions of developers worldwide who rely on GitHub for secure collaboration and version control.

The issue lies in the way GitHub generates and verifies commit hashes. A commit hash is a unique digital fingerprint assigned to each code change, allowing developers to track changes and verify the integrity of their codebase. However, researchers found that an attacker can manipulate a commit’s contents without altering its corresponding hash, effectively rewriting history. This exploit takes advantage of the way GitHub uses cryptographic techniques to sign commits, which can be bypassed using a sophisticated technique known as a “reversible signature scheme.”

The vulnerability affects all users who have committed code to GitHub repositories, regardless of their reputation or security measures in place. While the researchers demonstrated the attack on a small scale, its potential impact is significant, given the vast number of developers and organizations that rely on GitHub for secure collaboration. The implications are particularly concerning for open-source projects, where contributors often work anonymously, making it harder to identify and mitigate potential threats.

This exploit highlights the ongoing cat-and-mouse game between cybersecurity researchers and attackers. As AI-powered tools become increasingly effective in discovering vulnerabilities, hackers are finding new ways to bypass security measures. In this case, the reversible signature scheme used by GitHub provides an entry point for malicious actors to manipulate commit hashes without raising red flags.

The discovery of this vulnerability underscores the need for continuous monitoring and updates of software development platforms like GitHub. Developers must remain vigilant and adapt their workflows to stay ahead of emerging threats. This includes regularly reviewing commit logs, verifying changes made to sensitive code, and implementing additional security measures to detect potential attacks.

To safeguard against similar exploits in the future, developers should prioritize robust testing and validation of their codebase. Regularly scanning for vulnerabilities using AI-powered tools can also help identify potential weaknesses before they are exploited. By staying informed about emerging threats and adapting their workflows accordingly, developers can minimize the risk of costly data breaches and reputation damage.


Source: The Hacker News — 2026-07-08