Gitea · Gitea · published 2026-11-01

CVE-2026-117646Gitea private repository listing to public-only tokens on profiles

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-117646 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 9% of all CVEs. This Gitea vulnerability: CVSS 4.3 (v3.1). Fixed upstream in Gitea 28.3.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Gitea 28.3.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security release: 28.3.0

    Upgrade to 28.3.0

    Why: Vendor security release for server software (most severe: CVE-2026-120263).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (10th pct)FIRST EPSS v2026.06.15
CVSS base score4.3 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

The repositories, stars and watching tabs of user profiles and the repository list of organization home pages included private repositories for every signed-in request without checking whether the request used a personal access token restricted to public resources (`public-only`). A holder of such a token could list the private repositories visible to the token's owner, and that user's stars and watches of private repositories. The API and the profile activity tab already applied the restriction. The impact is disclosure of repository names and metadata, not of repository content.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →