<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 04:18:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-123638 — Gitea protected file pattern bypass with quoted file names</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-123638</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Gitea&lt;/p&gt;
&lt;p&gt;The &amp;#34;Protected file patterns&amp;#34; 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&amp;#39;s reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository&amp;#39;s runners. Changed files are now listed unquoted, and a rename reports both the old and the new path.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Gitea&lt;/p&gt;
&lt;p&gt;The &amp;#34;Protected file patterns&amp;#34; 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&amp;#39;s reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository&amp;#39;s runners. Changed files are now listed unquoted, and a rename reports both the old and the new path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-123638</guid>
    </item>
  </channel>
</rss>
