<?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:34:05 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1576 — De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaq…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1576</link>
      <description>certfr-2026-avi-1576</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1576</guid>
    </item>
    <item>
      <title>fkie_cve-2026-131265</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-131265</link>
      <description>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings for polling assets in the ingestion schedule view.
The vulnerability is possible because the ingestion schedule view does not verify the Assets view permission before it returns data derived from assets.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings for polling assets in the ingestion schedule view.
The vulnerability is possible because the ingestion schedule view does not verify the Assets view permission before it returns data derived from assets.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-131265</guid>
    </item>
    <item>
      <title>GHSA-6x22-29vh-j2g7</title>
      <link>https://db.gcve.eu/vuln/ghsa-6x22-29vh-j2g7</link>
      <description>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings for polling assets in the ingestion schedule view.
The vulnerability is possible because the ingestion schedule view does not verify the Assets view permission before it returns data derived from assets.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings for polling assets in the ingestion schedule view.
The vulnerability is possible because the ingestion schedule view does not verify the Assets view permission before it returns data derived from assets.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-6x22-29vh-j2g7</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4673 — Splunk SOAR: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4673</link>
      <description>&lt;p&gt;Ein authentisierter Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Berechtigungen zu erweitern, Administratorrechte zu erlangen, beliebigen Code mit dem Splunk SOAR-Dienstkonto oder Root-Rechten auszuführen, Cross-Site-Scripting-Angriffe durchzuführen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein authentisierter Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Berechtigungen zu erweitern, Administratorrechte zu erlangen, beliebigen Code mit dem Splunk SOAR-Dienstkonto oder Root-Rechten auszuführen, Cross-Site-Scripting-Angriffe durchzuführen oder einen Denial-of-Service-Zustand zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4673</guid>
    </item>
  </channel>
</rss>
