<?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:00.674271+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-131305</id>
    <title>CVE-2026-131305 — Improper Input Validation through the REST API in Splunk AI Assistant</title>
    <updated>2026-11-20T02:14:00.679195+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Splunk AI Assistant</p>
<p>In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.
The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-131305"/>
  </entry>
</feed>
