File-type restriction bypass via unchecked attachment renaming
Published Dec 26, 2025 · Updated Dec 26, 2025
File-type restriction bypass in Gitea before 1.23.0 allows remote authenticated users to rename attachments to forbidden extensions. The issue, comment, and release attachment API handlers wrote new names through repo_model.UpdateAttachment without rechecking the configured allowlist. An issue poster or user with repository write access can bypass instance-level extension restrictions; exploitation requires a nonempty allowlist.
Summary
What happened
File-type restriction bypass in Gitea before 1.23.0 allows remote authenticated users to rename attachments to forbidden extensions. The issue, comment, and release attachment API handlers wrote new names through repo_model.UpdateAttachment without rechecking the configured allowlist. An issue poster or user with repository write access can bypass instance-level extension restrictions; exploitation requires a nonempty allowlist.
The record
- CVE
- CVE-2025-68939
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-424, CAPEC-127, CAPEC-554, T1565.001
- 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.23.0
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.
Weakness, pattern, technique
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