CVE and update status of the FreeBSD ports tree3,755 unaddressed CVEs in 720 portsAll times are CET
CVE details

CVE-2026-118395

Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and `POST /api/v1/repos/{owner}/{repo}/generate` still accepted such tokens. A holder of a public-only token with the needed write scopes could create private repositories in organizations where the token's owner may create repositories, create private organizations, and generate private repositories from templates. The token still could not read the private repositories it created.

Score
–
Published
2026-11-01
Links
NVD · cve.org · Report wrong data

Matched ports (1)

PortPackageVersionStatusMaintainer
www/giteagitea28.2.0unaddressedports@foss-daily.org

Template for a VuXML entry

Check the content

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><lt>28.3.0</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-118395: Gitea 1.27.3 stopped personal access tokens
	  restricted to public resources (`public-only`) from creating
	  repositories through `POST /api/v1/user/repos` and `POST
	  /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST
	  /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and `POST
	  /api/v1/repos/{owner}/{repo}/generate` still accepted such tokens.
	  A holder of a public-only token with the needed write scopes could
	  create private repositories in organizations where the token's
	  owner may create repositories, create private organizations, and
	  generate private repositories from templates. The token still could
	  not read the private repositories it created.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-118395</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-118395</url>
    </references>
    <dates>
      <discovery>2026-11-01</discovery>
      <entry>2026-11-02</entry>
    </dates>
  </vuln>