CVE-2026-123642

Gitea pull request creation without pull request access through AGit

Published Nov 15, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The AGit workflow used by Gitea lets users push refs/for/... to create pull requests. This workflow erroneously omitted a re‑check of the pusher's pull‑request permissions when the PR object was instantiated. Consequently, a user or an SSH deploy key that was granted only read access to the repository, or write access to the wiki, could open pull requests in a repository where they had no PR rights. This bypass allows the attacker to introduce arbitrary code into the PR queue without being granted the necessary authorization, effectively creating a privilege escalation path for code injection and potential compromise of the repository.

Affected Systems

The flaw exists in all Gitea releases up to but not including version 28.4.0. An attacker can exploit the issue only if they have a Git or SSH access that can push to refs/for/... in any affected repository. The official fix is released in Gitea 28.4.0, which restores the missing permission check.

Risk and Exploitability

The attack vector is a non‑interactive Git push to refs/for/..., and it does not require any user interaction beyond a repository password or SSH key. No CVSS score is supplied, but the EPSS score is unavailable and KEV does not list it, suggesting that large‑scale exploitation is not currently observed. Nevertheless, the capability to create pull requests without appropriate rights provides an avenue for arbitrary code injection and potential compromise of the repository’s codebase, warranting immediate remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.4.0 or later to restore proper permission checks during pull‑request creation.
  • Disable or restrict AGit ref pushes (refs/for/...) for users or deploy keys that lack explicit pull‑request permissions.
  • Revoke any wiki‑write deploy keys that are not granted pull‑request access, and verify that SSH keys without PR rights cannot push to refs/for/...

Generated by OpenCVE AI on November 15, 2026 at 22:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Description 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.
Title Gitea pull request creation without pull request access through AGit
Weaknesses CWE-862
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Nov 15, 2026, 9:14 PM
Reserved
Nov 15, 2026, 8:31 PM
Status
Deferred
Published
Nov 15, 2026, 10:17 PM
Modified
Nov 15, 2026, 10:17 PM