Gitea · Gitea · published 2026-11-01

CVE-2026-119441Gitea public-only token bypass on bulk organization repository deletion

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-119441 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 17% of all CVEs. This Gitea vulnerability: CVSS 7.5 (v3.1), attacks can be automated. 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.3% (18th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

`DELETE /api/v1/orgs/{org}/repos` deletes all repositories of an organization, but it did not enforce the public-only restriction of access tokens: the route only checked that the organization itself was public. A public-only token of an owner of a public organization could therefore permanently delete the organization's private repositories, which such a token must not reach. Routes that require organization ownership now reject public-only tokens.

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 →