<?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:10 +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-131250</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-131250</link>
      <description>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the expected authorization scope.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the expected authorization scope.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-131250</guid>
    </item>
    <item>
      <title>GHSA-gq34-54q2-j779</title>
      <link>https://db.gcve.eu/vuln/ghsa-gq34-54q2-j779</link>
      <description>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the expected authorization scope.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary.
The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the expected authorization scope.
For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gq34-54q2-j779</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>
