https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 07:39:10 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1056 certfr-2026-avi-1056 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1056 https://cve.radiocsirt.org/vuln/euvd-2026-359228 EUVD-2026-359228 https://cve.radiocsirt.org/vuln/euvd-2026-359228 https://cve.radiocsirt.org/vuln/fkie_cve-2026-76391 <p>In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the &#34;admin&#34; or &#34;power&#34; Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.</p> <p>In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the &#34;admin&#34; or &#34;power&#34; Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-76391 https://cve.radiocsirt.org/vuln/ghsa-g2mq-q5g6-g67q <p>In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the &#34;admin&#34; or &#34;power&#34; Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.</p> <p>In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the &#34;admin&#34; or &#34;power&#34; Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.</p> https://cve.radiocsirt.org/vuln/ghsa-g2mq-q5g6-g67q