<?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://vulnerability.circl.lu</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>Sat, 03 Oct 2026 11:29:06 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14538</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-14538</link>
      <description>bdu:2026-14538</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-14538</guid>
    </item>
    <item>
      <title>BIT-gitlab-2026-85706 — Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab</title>
      <link>https://vulnerability.circl.lu/vuln/bit-gitlab-2026-85706</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: gitlab&lt;/p&gt;
&lt;p&gt;GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: gitlab&lt;/p&gt;
&lt;p&gt;GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bit-gitlab-2026-85706</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1160 — De multiples vulnérabilités ont été découvertes dans GitLab. Certaines d'entre elles permettent à un attaquant de provo…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1160</link>
      <description>certfr-2026-avi-1160</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1160</guid>
    </item>
    <item>
      <title>fkie_cve-2026-85706</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-85706</link>
      <description>&lt;p&gt;GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-85706</guid>
    </item>
    <item>
      <title>GHSA-f47w-mrg9-g9p2</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-f47w-mrg9-g9p2</link>
      <description>&lt;p&gt;GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-f47w-mrg9-g9p2</guid>
    </item>
    <item>
      <title>NCSC-2026-0367 — Kwetsbaarheid verholpen in GitLab Community en Enterprise Editions</title>
      <link>https://vulnerability.circl.lu/vuln/ncsc-2026-0367</link>
      <description>NCSC-2026-0367</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ncsc-2026-0367</guid>
    </item>
  </channel>
</rss>
