Package upload via dropped token scope
Published Dec 26, 2025 · Updated Dec 26, 2025
Authorization bypass in Gitea before 1.22.2 allows remote authenticated users with read-package tokens to upload packages. The NuGet, Conan, and container registry authentication handlers fail to carry the originating API token scope into package authorization, so a derived bearer token is treated without its read-only restriction. Possession of package-read access is sufficient to write package content through affected registry upload endpoints without broader package-write permission.
Summary
What happened
Authorization bypass in Gitea before 1.22.2 allows remote authenticated users with read-package tokens to upload packages. The NuGet, Conan, and container registry authentication handlers fail to carry the originating API token scope into package authorization, so a derived bearer token is treated without its read-only restriction. Possession of package-read access is sufficient to write package content through affected registry upload endpoints without broader package-write permission.
The record
- CVE
- CVE-2025-68944
- Published
- Dec 26, 2025
- Updated
- Dec 26, 2025
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-441, CAPEC-219, CAPEC-465, T1078
- 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.22.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.
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