<?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-20T00:58:14.490321+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-131176</id>
    <title>CVE-2026-131176 — Missing Authorization for HTML-Based Views through the REST API in Splunk Enterprise</title>
    <updated>2026-11-20T00:58:14.495714+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Splunk Enterprise</p>
<p>In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.17, a user that holds a role with the edit_own_objects capability but does not hold the edit_view_html capability could create or modify a private Hypertext Markup Language (HTML) view through the Representational State Transfer (REST) API.
The vulnerability is possible because the REST API applies the edit_own_objects capability when it creates or modifies private HTML-based views instead of requiring the edit_view_html capability.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-131176"/>
  </entry>
</feed>
