PatchSiren cyber security CVE debrief
CVE-2026-70407 Gitea CVE debrief
Gitea's organization-list API does not enforce the read:organization token scope, allowing tokens limited to other categories to retrieve organization metadata visible to their owners. Site administrators' tokens can include Limited and private organizations, bypassing intended restrictions. This issue affects Gitea versions up to 1.27.2 and requires immediate attention from site administrators and defenders responsible for Gitea instances. They should assess exposure and verify configurations to prevent unauthorized access to organization metadata.
- Vendor
- Gitea
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-14
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-14
- Advisory updated
- 2026-10-14
Who should care
Site administrators and defenders responsible for Gitea instances should assess exposure and verify configurations to prevent unauthorized access to organization metadata. They should prioritize verifying Gitea instance configurations, especially those with site administrator tokens, and assess exposure of organization metadata. Defenders should also review compensating controls for exposed systems while remediation is scheduled and verified.
Why it matters
Defenders should prioritize verifying Gitea instance configurations and assessing exposure of organization metadata due to the token scope bypass vulnerability.
- Potential unauthorized access to organization metadata
- Bypassing of intended token scope restrictions
- Increased risk for site administrators with Limited and private organizations
Technical summary
Gitea's organization-list API fails to enforce the read:organization token scope, permitting tokens with other scopes to access organization metadata. This issue affects Gitea versions up to 1.27.2 and requires immediate attention from site administrators and defenders responsible for Gitea instances. They should assess exposure and verify configurations to prevent unauthorized access to organization metadata. The vulnerability has been confirmed in Gitea versions up to 1.27.2, and defenders should prioritize verifying Gitea instance configurations and assessing exposure of organization metadata.
Defensive priority
Defenders should prioritize verifying Gitea instance configurations, especially those with site administrator tokens, and assess exposure of organization metadata.
Recommended defensive actions
- Verify Gitea instance configurations to ensure proper token scope enforcement
- Assess exposure of organization metadata for site administrator tokens
- Update Gitea to version 1.27.3 or later
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE Program record and NVD vulnerability detail provide official information on the vulnerability. Gitea's security advisory and release notes offer additional context. The vulnerability has been confirmed in Gitea versions up to 1.27.2. Defenders should verify Gitea instance configurations and assess exposure of organization metadata. Evidence is limited to publicly available information, and further verification is required.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-70407 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-70407
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-70407 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-70407
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Gitea organization listing token scope bypass
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/70xxx/CVE-2026-70407.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/security/advisories/GHSA-ww9q-7j5q-hrv5
Supplemental source - vendor-advisory
-
Source reference
Unverified legacy reference
URL: https://blog.gitea.com/release-of-1.27.3/
Supplemental source - release-notes
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39041
Supplemental source - patch
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39058
Supplemental source - patch
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/releases/tag/v1.27.3
Supplemental source - release-notes
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.