Gitea: Missing repository-unit authorization on issue-template API endpoints

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-27783: 0.35% estimated exploitation activity in the next 30 days; percentile 28.78 (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 Three Gitea API endpoints — GET /repos/{owner}/{repo}/issuetemplates, GET /repos/{owner}/{repo}/issueconfig and GET /repos/{owner}/{repo}/issueconfig/validate — read files from the repository's Code default branch (.gitea/ISSUETEMPLATE/ and issueconfig.yaml) and return their contents, but are registered without the reqRepoReader(unit.TypeCode) authorization middleware that every sibling Code-tree endpoint in the same route group carries. A user who has access to a private repository through any single repository unit (for example an organization team granted only the Issues unit, with no Code access) can therefore read the issue-template and issue-config files of that repository's Code tree, which their permission set should not expose. --- Root cause The three endpoints lack the unit guard routers/api/v1/api.go:1433-1437: m.Get("/issuetemplates", context.ReferencesGitRepo(), repo.GetIssueTemplates) m.Get("/issueconfig", context.ReferencesGitRepo(), repo.GetIssueConfig)…

Published by the source

16 Jun 2026, 23:41 UTC

Last modified by the source

16 Jun 2026, 23:41 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3fwp-p5rj-2pxf

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

# Patch Next advisory brief: CVE-2026-27783

Advisory: Gitea: Missing repository-unit authorization on issue-template API endpoints
IDs: CVE-2026-27783, GHSA-3fwp-p5rj-2pxf
Record: https://patchnext.com/advisories/cve-2026-27783 (revision 1, source checked 26 Oct 2026, 15:24 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.26.2. A vendor fix does not mean a deployment is fixed.

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

## 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-3fwp-p5rj-2pxf (GitHub-reviewed advisory GHSA-3fwp-p5rj-2pxf lists affected ranges: Go code.gitea.io/gitea >=0 <=1.26.1)

Commands are suggestions: review each one before running it.