<?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, 20 Nov 2026 01:46:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-131270 — Path Traversal through the REST API in Splunk SOAR</title>
      <link>https://db.gcve.eu/vuln/cve-2026-131270</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Splunk SOAR&lt;/p&gt;
&lt;p&gt;In Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to write files outside the configured repository, which lets the user modify files that the user account running Splunk SOAR can write to.
The vulnerability is possible because Splunk SOAR does not require source control repository paths to remain inside the configured repository.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Splunk SOAR&lt;/p&gt;
&lt;p&gt;In Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to write files outside the configured repository, which lets the user modify files that the user account running Splunk SOAR can write to.
The vulnerability is possible because Splunk SOAR does not require source control repository paths to remain inside the configured repository.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-131270</guid>
    </item>
  </channel>
</rss>
