CVE-2026-119441
`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.
- Score
- –
- Published
- 2026-11-01
- Links
- NVD · cve.org · Report wrong data
Matched ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| www/gitea | gitea | 28.2.0 | 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.27.0</ge><lt>28.3.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>CVE-2026-119441: `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.</p>
</body>
</description>
<references>
<cvename>CVE-2026-119441</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-119441</url>
</references>
<dates>
<discovery>2026-11-01</discovery>
<entry>2026-11-02</entry>
</dates>
</vuln>