Protected release deletion via publisher identity check
Published Dec 26, 2025 · Updated Dec 26, 2025
Incorrect authorization in Gitea before 1.25.2 allows remote authenticated users to delete protected releases through repository APIs. DeleteReleaseByID checks whether the release publisher, rather than the requesting user, may control the protected tag associated with the release. Exploitation requires authenticated access to a release-deletion path and a release whose publisher is allowed to control its protected tag.
Summary
What happened
Incorrect authorization in Gitea before 1.25.2 allows remote authenticated users to delete protected releases through repository APIs. DeleteReleaseByID checks whether the release publisher, rather than the requesting user, may control the protected tag associated with the release. Exploitation requires authenticated access to a release-deletion path and a release whose publisher is allowed to control its protected tag.
The record
- CVE
- CVE-2025-68938
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-863, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 26, 2025CVE publishedPublication date reported by the CVE source.
- Dec 26, 2025Record 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 <1.25.2
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
No public exploit references are available in this record.
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