Writer-level branch deletion via missing authorization
Published Feb 19, 2026 · Updated Feb 19, 2026
Incorrect authorization in Gogs before 0.14.1 allows remote authenticated users with repository write access to delete protected branches. DeleteBranchPost checks write access and branch existence but never rejects a protected or default branch before force-deleting it. Exploitation requires web-interface access and configured branch protection; default-branch deletion interrupts clone and pull access and permits replacement.
Summary
What happened
Incorrect authorization in Gogs before 0.14.1 allows remote authenticated users with repository write access to delete protected branches. DeleteBranchPost checks write access and branch existence but never rejects a protected or default branch before force-deleting it. Exploitation requires web-interface access and configured branch protection; default-branch deletion interrupts clone and pull access and permits replacement.
The record
- CVE
- CVE-2026-25232
- Published
- Feb 19, 2026
- Updated
- Feb 19, 2026
- Vendor
- Gogs
- Product
- Gogs
- Classifications
- CWE-863, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2026CVE publishedPublication date reported by the CVE source.
- Feb 19, 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.14.1
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
- Direct protected-branch deletion POST proof of conceptproof of concept · unverified
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