Gitea · Gitea · published 2026-11-01

CVE-2026-119625Gitea user and organization feed token scope bypass

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-119625 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 15% 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% (16th 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 `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as `read:issue`, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require `read:user` or `read:organization`.

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 →