CVE-2026-123642
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.
- Score
- –
- Published
- 2026-11-15
- Links
- NVD · cve.org · Report wrong data
Matched ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| www/gitea | gitea | 28.3.0_1 | unaddressed | ports@foss-daily.org |
Template for a VuXML entry
Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.
Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>gitea -- FIXME</topic>
<affects>
<package>
<name>gitea</name>
<range><ge>1.16.0</ge><lt>28.4.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CVE-2026-123642: 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.</p>
</body>
</description>
<references>
<cvename>CVE-2026-123642</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-123642</url>
</references>
<dates>
<discovery>2026-11-15</discovery>
<entry>2026-11-16</entry>
</dates>
</vuln>