Metadata disclosure via misordered token scope middleware
Published Oct 14, 2026 · Updated Oct 14, 2026
Authorization bypass in Gitea 1.27.2 and earlier allows remote authenticated users to read organization metadata via its API. In routers/api/v1/api.go, the organization-list route places tokenRequiresScopes after org.GetAll, allowing the listing handler to respond before the required scope check. Exploitation requires a valid token lacking read:organization; disclosure is limited to metadata visible to its owner, including Limited and private organizations for a site administrator.
Summary
What happened
Authorization bypass in Gitea 1.27.2 and earlier allows remote authenticated users to read organization metadata via its API. In routers/api/v1/api.go, the organization-list route places tokenRequiresScopes after org.GetAll, allowing the listing handler to respond before the required scope check. Exploitation requires a valid token lacking read:organization; disclosure is limited to metadata visible to its owner, including Limited and private organizations for a site administrator.
The record
- CVE
- CVE-2026-70407
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- CWE-285
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 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.27.2
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started