<?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>Wed, 18 Nov 2026 13:23:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-105929</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-105929</link>
      <description>&lt;p&gt;A path traversal vulnerability (CWE-22) was found in ansible-core&amp;#39;s ansible-galaxy role installation. An explicit role &amp;#34;name&amp;#34; taken from a role&amp;#39;s meta/requirements.yml is used to construct the on-disk installation path without validating that the resulting destination stays within the selected roles directory. A name containing &amp;#34;../&amp;#34; escapes that directory, and an absolute name replaces it entirely. Because ansible-galaxy processes transitive dependencies from an installed role&amp;#39;s meta/requirements.yml, a malicious role publisher can cause attacker-supplied files to be written outside the operator&amp;#39;s chosen roles directory when the operator installs the role, and, when --force is used, can cause an existing role directory outside that path to be removed and replaced. The impact is bounded by the invoking user&amp;#39;s filesystem permissions and requires the operator to install the attacker-influenced content.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A path traversal vulnerability (CWE-22) was found in ansible-core&amp;#39;s ansible-galaxy role installation. An explicit role &amp;#34;name&amp;#34; taken from a role&amp;#39;s meta/requirements.yml is used to construct the on-disk installation path without validating that the resulting destination stays within the selected roles directory. A name containing &amp;#34;../&amp;#34; escapes that directory, and an absolute name replaces it entirely. Because ansible-galaxy processes transitive dependencies from an installed role&amp;#39;s meta/requirements.yml, a malicious role publisher can cause attacker-supplied files to be written outside the operator&amp;#39;s chosen roles directory when the operator installs the role, and, when --force is used, can cause an existing role directory outside that path to be removed and replaced. The impact is bounded by the invoking user&amp;#39;s filesystem permissions and requires the operator to install the attacker-influenced content.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-105929</guid>
    </item>
    <item>
      <title>GHSA-65g3-4m89-fc5m</title>
      <link>https://db.gcve.eu/vuln/ghsa-65g3-4m89-fc5m</link>
      <description>&lt;p&gt;A path traversal vulnerability (CWE-22) was found in ansible-core&amp;#39;s ansible-galaxy role installation. An explicit role &amp;#34;name&amp;#34; taken from a role&amp;#39;s meta/requirements.yml is used to construct the on-disk installation path without validating that the resulting destination stays within the selected roles directory. A name containing &amp;#34;../&amp;#34; escapes that directory, and an absolute name replaces it entirely. Because ansible-galaxy processes transitive dependencies from an installed role&amp;#39;s meta/requirements.yml, a malicious role publisher can cause attacker-supplied files to be written outside the operator&amp;#39;s chosen roles directory when the operator installs the role, and, when --force is used, can cause an existing role directory outside that path to be removed and replaced. The impact is bounded by the invoking user&amp;#39;s filesystem permissions and requires the operator to install the attacker-influenced content.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A path traversal vulnerability (CWE-22) was found in ansible-core&amp;#39;s ansible-galaxy role installation. An explicit role &amp;#34;name&amp;#34; taken from a role&amp;#39;s meta/requirements.yml is used to construct the on-disk installation path without validating that the resulting destination stays within the selected roles directory. A name containing &amp;#34;../&amp;#34; escapes that directory, and an absolute name replaces it entirely. Because ansible-galaxy processes transitive dependencies from an installed role&amp;#39;s meta/requirements.yml, a malicious role publisher can cause attacker-supplied files to be written outside the operator&amp;#39;s chosen roles directory when the operator installs the role, and, when --force is used, can cause an existing role directory outside that path to be removed and replaced. The impact is bounded by the invoking user&amp;#39;s filesystem permissions and requires the operator to install the attacker-influenced content.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-65g3-4m89-fc5m</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:12448-1 — ansible-core-2.21.6-1.1 on GA media</title>
      <link>https://db.gcve.eu/vuln/opensuse-su-2026:12448-1</link>
      <description>&lt;p&gt;ansible-core-2.21.6-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ansible-core-2.21.6-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/opensuse-su-2026:12448-1</guid>
    </item>
  </channel>
</rss>
