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

CVE-2026-123638

The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double quote, a backslash or a control character. Such names never matched a pattern, so a user with write access could add or change files under a protected pattern by direct push or through a pull request merge, and could move a protected file out of the pattern's reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository's runners. Changed files are now listed unquoted, and a rename reports both the old and the new path.

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

Matched ports (1)

PortPackageVersionStatusMaintainer
www/giteagitea28.3.0_1unaddressedports@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.4.0</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-123638: The "Protected file patterns" setting of a branch
	  protection rule was checked against file names as git prints them,
	  and git quotes names that contain a double quote, a backslash or a
	  control character. Such names never matched a pattern, so a user
	  with write access could add or change files under a protected
	  pattern by direct push or through a pull request merge, and could
	  move a protected file out of the pattern's reach by renaming it.
	  Where the patterns protect workflow files, this allowed adding a
	  workflow that then ran on the repository's runners. Changed files
	  are now listed unquoted, and a rename reports both the old and the
	  new path.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-123638</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-123638</url>
    </references>
    <dates>
      <discovery>2026-11-15</discovery>
      <entry>2026-11-16</entry>
    </dates>
  </vuln>