Gitea · Gitea · published 2026-10-14
CVE-2026-70406Gitea private comparison disclosure with public-only tokens
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-70406 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 28% of all CVEs. This Gitea vulnerability: CVSS 6.5 (v3.1). Fixed upstream in Gitea 1.27.3, 1.27.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 1.27.3, 1.27.0.
Patch events
DevOpsGitea
Gitea security releases: 1.27.3, 1.27.0
Upgrade to
1.27.31.27.0Why: Vendor security release for server software (most severe: CVE-2026-70406).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (28th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.5 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0through1.27.2(affected)
Description (from the CVE record)#
Gitea's shared comparison helper omits the token repository-access check used when updating pull requests. A public-only token with read:repository scope can route a comparison or pull request creation through a public base repository and retrieve commit history and diffs from a private head repository accessible to the token owner. This bypasses the token's public-only restriction; it does not remove the account's underlying repository permission checks.
Quoted from the CVE Program record.