PatchSiren cyber security CVE debrief
CVE-2026-112887 Gitea CVE debrief
CVE-2026-112887 debrief based on CVE Program and NIST NVD records. Gitea Actions task tokens could be used to list repositories on the instance, including private ones, but not their contents. System users now own nothing, and `/api/v1/user` routes have restricted access. The vulnerability allows an attacker with workflow execution permissions to list all repositories on the Gitea instance, including private ones, using a Gitea Actions task token. This could lead to unauthorized access to repository metadata.
- Vendor
- Gitea
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-11-01
- Original CVE updated
- 2026-11-01
- Advisory published
- 2026-11-01
- Advisory updated
- 2026-11-01
Who should care
Defenders and administrators of Gitea instances should assess exposure of workflow tokens and restrict access to repository metadata. They should verify configurations, assess exposure, and restrict access to repository metadata to prevent unauthorized listing of private repositories.
Why it matters
CVE-2026-112887 allows listing of repositories on a Gitea instance using a workflow token, but repository contents remain protected. Defenders should verify configurations, assess exposure, and restrict access to repository metadata.
- Repository metadata exposure to unauthorized users
- Potential for unauthorized listing of private repositories
- Need for verification of Gitea instance configurations
- Requirement for restricted access to repository metadata
Technical summary
Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, allowing listing of repositories on the instance, including private ones, but not their contents. System users now own nothing, and `/api/v1/user` routes have restricted access. The vulnerability allows an attacker with workflow execution permissions to list all repositories on the Gitea instance, including private ones, using a Gitea Actions task token. This could lead to unauthorized access to repository metadata, potentially allowing attackers to gather information about the instance's repository structure.
Defensive priority
Defenders should verify Gitea instance configurations, assess exposure of workflow tokens, and restrict access to repository metadata.
Recommended defensive actions
- Verify Gitea instance configurations to restrict workflow token access
- Assess exposure of workflow tokens to unauthorized users
- Restrict access to repository metadata
- Monitor for suspicious repository listing activity
- 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
Evidence notes
Evidence from CVE Program and NIST NVD records indicates that Gitea Actions task tokens could be used to list repositories. Repository contents remained protected by per-repository permission checks. The CVE Program and NIST NVD records confirm that Gitea Actions task tokens authenticate to the REST API as a shared system user with a negative ID, allowing listing of repositories on the instance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-112887 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-112887
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-112887 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-112887
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://blog.gitea.com/release-of-28.3.0/
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/39945
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/pull/40115
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/releases/tag/v28.3.0
88ee5874-cf24-4952-aea0-31affedb7ff2
-
Source reference
Unverified legacy reference
URL: https://github.com/go-gitea/gitea/security/advisories/GHSA-8r36-6j2c-3gmv
88ee5874-cf24-4952-aea0-31affedb7ff2
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.