Repository read and write via ignored bearer scopes
Published Jul 3, 2026 · Updated Jul 3, 2026
Incorrect authorization in Gitea 1.26.1 and earlier allows remote authenticated users to read or write repositories via bearer tokens. CheckRepoScopedToken returns without enforcing the recorded repository scope when IsBasicAuth is false, causing Git smart HTTP to ignore PAT and OAuth2 bearer scopes. A valid token and normal repository RBAC are required; the bypass defeats token scopes but does not expand the token owner's repository access.
Summary
What happened
Incorrect authorization in Gitea 1.26.1 and earlier allows remote authenticated users to read or write repositories via bearer tokens. CheckRepoScopedToken returns without enforcing the recorded repository scope when IsBasicAuth is false, causing Git smart HTTP to ignore PAT and OAuth2 bearer scopes. A valid token and normal repository RBAC are required; the bypass defeats token scopes but does not expand the token owner's repository access.
The record
- CVE
- CVE-2026-28744
- Published
- Jul 3, 2026
- Updated
- Jul 3, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 3, 2026CVE publishedPublication date reported by the CVE source.
- Jul 3, 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 <=1.26.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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