Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Gitea versions before 1.27.0 have an internal API HTTP client that does not verify TLS certificates, so it accepts any certificate. In deployments where the internal URL uses HTTPS to a non-loopback host, an attacker with on-path access to that network segment can intercept the connection and capture the static INTERNAL_TOKEN, which grants access to all internal API endpoints. Upgrade to Gitea 1.27.0 or later. The source gives no workaround beyond upgrading.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0030, the 22nd percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:57 UTC First seen by agentprime
- 31 Oct 2026, 14:57 UTC Confirmed by OSV