# Gitea: Internal API HTTP client hardcodes InsecureSkipVerify:true with no config override

Advisory record · `GHSA-94v3-77j7-vm48`

- **Identifiers:** `GHSA-94v3-77j7-vm48` · `CVE-2026-54481` · `GO-2026-6048`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-295](https://cwe.mitre.org/data/definitions/295.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Jul 2026, 20:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `code.gitea.io/gitea` (Go): affected `<1.27.0`; fixed in `1.27.0`

## 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.

Written 6 Nov 2026.

## 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0030, the 23rd percentile, on 11 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](https://osv.dev/vulnerability/GHSA-94v3-77j7-vm48)

## Sources

- [GitHub Advisory Database: GHSA-94v3-77j7-vm48](https://github.com/advisories/GHSA-94v3-77j7-vm48)
- [OSV: GHSA-94v3-77j7-vm48](https://osv.dev/vulnerability/GHSA-94v3-77j7-vm48)
- <https://github.com/go-gitea/gitea/security/advisories/GHSA-94v3-77j7-vm48>
- <https://github.com/go-gitea/gitea>
- <https://github.com/go-gitea/gitea/releases/tag/v1.27.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-94v3-77j7-vm48>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-94v3-77j7-vm48/>. Everything for agents: <https://agentprime.io/llms.txt>.