Gitea · Gitea · published 2026-11-15

CVE-2026-123642Gitea pull request creation without pull request access through AGit

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-123642 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.4.0, 28.3.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Gitea 28.4.0, 28.3.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security releases: 28.4.0, 28.3.0

    Upgrade to 28.4.028.3.0

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

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (9th 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:N/I:L/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 AGit flow (pushing to `refs/for/...`) did not check the pusher's access to pull requests again when it created the pull request. A user or deploy key with read access to the code only, or with write access to the wiki over SSH, could open pull requests in a repository where they have no access to pull requests. Creating a pull request through AGit now requires read access to the pull requests of the repository and is refused for wiki pushes.

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 →