<?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-20T02:14:19.584761+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/cve-2026-131300</id>
    <title>CVE-2026-131300 — Sensitive Information Disclosure through the REST API in Splunk App for Stream</title>
    <updated>2026-11-20T02:14:19.585982+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Splunk App for Stream</p>
<p>In Splunk App for Stream versions below 8.1.7, a user who can read splunkd_access.log or the _internal Splunk index could recover the Stream forwarder authentication key and use it to impersonate a trusted Stream forwarder.
The vulnerability is possible because Splunk App for Stream sends the authentication key in an internal request URL, and Splunk records that URL in splunkd_access.log.
For more information see About Splunk Stream (https://help.splunk.com/en/splunk-enterprise/collect-stream-data/install-and-configure-splunk-stream/8.1/introduction/about-splunk-stream) and restmap.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.3-configuration-file-reference/restmap.conf) in the Splunk documentation.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-131300"/>
  </entry>
</feed>
