Gitea: Personal access token scope enforcement bypass on the repository home page (GET /{owner}/{repo}) discloses private repository contents

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-58444: 0.36% estimated exploitation activity in the next 30 days; percentile 29.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A personal access token (PAT) or OAuth2 token that does not carry the repository scope or that is public-only is correctly rejected (HTTP 403) by the recently hardened web content routes (archive download, raw/media file download, and repository RSS/Atom feeds). However, the repository home page route GET /{owner}/{repo} (handler repo.Home) serves the private repository's rendered README, root file/directory tree, description, language statistics, license, and latest-release information to that same token. This is a token-scope enforcement bypass and private-repository content disclosure. It is the same source→sink pattern already fixed for neighbouring routes in: - GHSA-cr4g-f395-h25h (CVE-2026-20706) token scope bypass on web archive download - GHSA-3pww-vcvm-3gmj (CVE-2026-27761) token scope bypass on repository RSS/Atom feeds repo.Home is the remaining token-auth-enabled content route that was not given the guard. Details / Root cause Web routes accept token…

Published by the source

21 Jul 2026, 20:38 UTC

Last modified by the source

21 Jul 2026, 20:38 UTC

Source last checked

26 Oct 2026, 15:27 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cp3q-vrj2-ghhh

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-58444

Advisory: Gitea: Personal access token scope enforcement bypass on the repository home page (`GET /{owner}/{repo}`) discloses private repository contents
IDs: CVE-2026-58444, GHSA-cp3q-vrj2-ghhh
Record: https://patchnext.com/advisories/cve-2026-58444 (revision 1, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: code.gitea.io/gitea 1.27.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go code.gitea.io/gitea: affected < 1.27.0; fixed in 1.27.0

## Suggested inspection (read-only)
- Go code.gitea.io/gitea: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on code.gitea.io/gitea.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cp3q-vrj2-ghhh (GitHub-reviewed advisory GHSA-cp3q-vrj2-ghhh lists affected ranges: Go code.gitea.io/gitea >=0 <1.27.0)

Commands are suggestions: review each one before running it.