<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T01:08:49.162406+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/certfr-2026-avi-1576</id>
    <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>
    <updated>2026-11-20T01:08:49.164335+00:00</updated>
    <content>certfr-2026-avi-1576</content>
    <link href="https://db.gcve.eu/vuln/certfr-2026-avi-1576"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-131186</id>
    <title>fkie_cve-2026-131186</title>
    <updated>2026-11-20T01:08:49.164385+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user that holds a role with the list_deployment_server capability could access sensitive information from inputs.conf files outside the intended deployment app directory through the Representational State Transfer (REST) API.
The vulnerability is possible because the REST API does not restrict a deployment app name to an existing deployment app before reading input configurations.
For more information see authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.4-configuration-file-reference/authorize.conf), Deployment server architecture (https://help.splunk.com/en/splunk-enterprise/administer/update-your-deployment/9.0/deployment-server-and-forwarder-management/deployment-server-architecture), and inputs.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.16-configuration-file-reference/inputs.conf) in the Splunk documentation.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-131186"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-g2r3-c8qc-36w8</id>
    <title>GHSA-g2r3-c8qc-36w8</title>
    <updated>2026-11-20T01:08:49.164424+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user that holds a role with the list_deployment_server capability could access sensitive information from inputs.conf files outside the intended deployment app directory through the Representational State Transfer (REST) API.
The vulnerability is possible because the REST API does not restrict a deployment app name to an existing deployment app before reading input configurations.
For more information see authorize.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.4-configuration-file-reference/authorize.conf), Deployment server architecture (https://help.splunk.com/en/splunk-enterprise/administer/update-your-deployment/9.0/deployment-server-and-forwarder-management/deployment-server-architecture), and inputs.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.16-configuration-file-reference/inputs.conf) in the Splunk documentation.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-g2r3-c8qc-36w8"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/wid-sec-w-2026-4674</id>
    <title>WID-SEC-W-2026-4674 — Splunk Enterprise: Mehrere Schwachstellen</title>
    <updated>2026-11-20T01:08:49.164447+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Splunk Enterprise ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder seine Rechte zu erweitern.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/wid-sec-w-2026-4674"/>
  </entry>
</feed>
