<?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://db.gcve.eu</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>Fri, 23 Oct 2026 04:12:47 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1363 — De multiples vulnérabilités ont été découvertes dans GitLab. Certaines d'entre elles permettent à un attaquant de provo…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1363</link>
      <description>certfr-2026-avi-1363</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1363</guid>
    </item>
    <item>
      <title>fkie_cve-2026-103515</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-103515</link>
      <description>&lt;p&gt;GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group&amp;#39;s Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group&amp;#39;s Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-103515</guid>
    </item>
    <item>
      <title>GHSA-x828-vfgm-5mgh</title>
      <link>https://db.gcve.eu/vuln/ghsa-x828-vfgm-5mgh</link>
      <description>&lt;p&gt;GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group&amp;#39;s Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group&amp;#39;s Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-x828-vfgm-5mgh</guid>
    </item>
    <item>
      <title>NCSC-2026-0447 — Kwetsbaarheden verholpen in GitLab door GitLab Inc.</title>
      <link>https://db.gcve.eu/vuln/ncsc-2026-0447</link>
      <description>NCSC-2026-0447</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ncsc-2026-0447</guid>
    </item>
  </channel>
</rss>
