Pre-commit control bypass via default no-verify flag
Published May 31, 2026 · Updated May 31, 2026
Protection mechanism failure in Aider 0.86.3 allows remote authenticated users to commit code without running pre-commit hooks. The git-commit-verify option defaults to false in aider/args.py, and GitRepo.commit in aider/repo.py then appends --no-verify to the Git commit command. The bypass is reached when Aider automatically commits generated changes in a repository that relies on pre-commit hooks, allowing prohibited code or secrets to enter Git history.
Summary
What happened
Protection mechanism failure in Aider 0.86.3 allows remote authenticated users to commit code without running pre-commit hooks. The git-commit-verify option defaults to false in aider/args.py, and GitRepo.commit in aider/repo.py then appends --no-verify to the Git commit command. The bypass is reached when Aider automatically commits generated changes in a repository that relies on pre-commit hooks, allowing prohibited code or secrets to enter Git history.
The record
- CVE
- CVE-2026-10174
- Published
- May 31, 2026
- Updated
- May 31, 2026
- Vendor
- Aider-AI
- Product
- Aider
- Classifications
- CWE-693, T1685
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 31, 2026CVE publishedPublication date reported by the CVE source.
- May 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.86.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Default runtime commits bypass pre-commit hooks via --no-verifyproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo