Splunk
Monthly
Log injection in @logtape/syslog allows network-accessible attackers to forge arbitrary syslog records in downstream collectors such as rsyslog, Splunk, and Elastic Stack. The escapeStructuredDataValue() function omits C0 control character escaping, so a literal newline embedded in a log property value terminates the current RFC 6587 TCP syslog frame and begins a new one; if the attacker-supplied bytes constitute a valid RFC 5424 header, the downstream collector accepts them as a separate, authentic-looking record. A second injection path exists through unvalidated SD-NAME keys, which can prematurely close structured-data elements. Both paths require the non-default SyslogSinkOptions.includeStructuredData: true setting. Publicly available proof-of-concept code exists; no CISA KEV listing at time of analysis.
Operating-system command execution in the Splunk MCP Server app (all versions below 1.2.1) lets a user already holding the Splunk 'admin' role run arbitrary commands on the underlying host by abusing unsafe deserialization in the credential-management component. Because the app trusts stored data and deserializes it without verifying the object type, a privileged Splunk user can escalate from application-level administration to full host compromise. No public exploit identified at time of analysis, and it is not listed in CISA KEV; a vendor patch is available.
Certificate validation bypass in Splunk Connect for Kafka below version 2.2.7 allows a network-positioned unauthenticated attacker to intercept and modify event data in transit to Splunk Enterprise's HTTP Event Collector when Kerberos authentication is configured. The Kerberos code path fails to apply the connector's configured TLS certificate validation options when constructing the HTTP client, effectively negating transport security despite HEC's TLS configuration. No active exploitation has been identified (not in CISA KEV), but the confidentiality and integrity impact on Splunk-ingested telemetry data is high.
Unauthenticated access to the Kafka Connect REST API in Splunk Connect for Kafka versions below 2.2.7 enables an SSRF-class attack that reconfigures the HTTP Event Collector destination to an attacker-controlled endpoint, resulting in theft of HEC authentication credentials and partial manipulation of event delivery to Splunk Enterprise. The connector's HEC endpoint validation does not enforce secure transport by default, meaning a non-TLS HTTP destination can be substituted without any authentication. No public exploit has been identified at time of analysis, but the attack requires no privileges and trivially low complexity, making any deployment with a network-exposed Kafka Connect REST API immediately actionable.
Splunk AI Toolkit before version 6.0.1 allows authenticated users holding the built-in 'power' role to modify app-provided scheduled searches, which execute SPL under the permissions of the search owner rather than the modifying user. By injecting arbitrary SPL into such searches, a 'power' role user can access all data visible to the search owner and alter system integrity - effectively escalating privileges beyond their authorization level. No public exploit code or active exploitation has been identified at time of analysis.
Unauthorized cross-user data access and deletion in Splunk AI Toolkit below 6.0.0 allows any authenticated user holding the 'power' Splunk role to read and destroy experiment history records belonging to other users. The root cause is CWE-639 (IDOR): the toolkit fails to preserve a trusted experiment scope boundary when processing caller-controlled query values, enabling horizontal privilege escalation across all experiment history without touching admin-level permissions. No active exploitation or public exploit code has been identified at time of analysis; a vendor-released patch (6.0.0) is available per Splunk advisory SVD-2026-0808.
Improper access control in Splunk AI Toolkit versions below 6.0.0 allows an authenticated user holding the schedule_search capability to deserialize arbitrary model files by invoking the apply search command via a scheduled search. Because the toolkit does not designate apply as a risky command, Splunk's built-in risky-command access controls are never triggered, enabling privilege escalation beyond what the role should permit. A vendor-released patch exists (version 6.0.0); no public exploit or CISA KEV listing has been identified at time of analysis.
Arbitrary code execution in Splunk AI Toolkit below 6.0.0 is achievable by any user holding the Splunk 'power' role, through loading a crafted model file that embeds malicious pickle payloads inside sparse matrix data. The toolkit's model codec deserializes this data without sanitizing or restricting the embedded pickle content, granting the attacker code execution as the Splunk server process. No public exploit or CISA KEV listing has been identified at time of analysis, but the RCE impact with a low-privilege network vector makes this a high-priority patch target for any Splunk deployment running the AI or Machine Learning Toolkit.
Missing authorization checks across multiple REST API handlers in Splunk AI Toolkit versions below 6.0.0 allow any low-privileged authenticated Splunk user - one who holds neither the 'admin' nor 'power' role - to start, stop, and reconfigure containers and to read or modify sensitive connection and configuration data. The vulnerability stems from CWE-862 (Missing Authorization), where the REST endpoints simply omit role-based access enforcement rather than incorrectly implementing it. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the low attack complexity and the fact that it was reported by Cisco make it a credible near-term target.
Privilege escalation in Splunk AI Toolkit before 6.0.0 allows any authenticated low-privileged user to operate with system-level permissions by exploiting a session key substitution flaw in the Agent Run History handler. The handler unconditionally replaces the caller's session key with a system authentication token before executing searches, completely bypassing Splunk's role-based access controls that gate elevated operations behind 'admin' or 'power' roles. This grants unauthorized read access to all indexed data, cross-user search job enumeration and deletion, and write-level system integrity impact - no public exploit has been identified at time of analysis, but the low exploitation complexity and clear mechanism description make this a high-priority patching target for Splunk enterprise deployments.
Server-Side Request Forgery (SSRF) in Cisco Talos Intelligence for Enterprise Security Cloud (versions below 1.0.3) allows an authenticated Splunk user holding the get_talos_enrichment capability to redirect the instance's outbound authenticated management requests to an attacker-controlled server, exposing Splunk management tokens. Successful exploitation grants the attacker full control over the Splunk instance, compromising the confidentiality, integrity, and availability of all data and configurations within it. No public exploit code or CISA KEV listing has been identified at time of analysis, but the patch is available and the CVSS score of 8.8 reflects the severity of token theft as a post-exploitation path.
Privilege escalation in Splunk Enterprise Security below 8.6.1 enables authenticated users holding the ess_analyst role to modify UEBA search macros that are subsequently executed by scheduled searches running under administrator permissions. The flaw stems from misconfigured UEBA app metadata that incorrectly grants analyst-tier write access to macros intended to be restricted to administrators, resulting in unauthorized access to all Splunk-indexed data and potential system integrity violations. No public exploit or CISA KEV listing exists at time of analysis, though the low barrier - any ess_analyst account - makes insider threat and compromised analyst credential scenarios credible attack paths.
SPL injection in Splunk Enterprise Security versions below 8.6.1 allows low-privileged authenticated users holding the mc_investigation_read capability to inject Search Processing Language through Analyst Queue search filter field names, gaining access to data and system integrity controls available to scheduled search contexts beyond their authorized scope. The root cause is absent validation of filter field names before inclusion in SPL queries - analogous to SQL injection but within Splunk's proprietary query language. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the CVSS 8.1 High score reflects meaningful confidentiality and integrity exposure for any account holding the relevant capability.
Improper TLS certificate validation in Splunk SOAR's CyberArk REST client exposes all credential vault traffic to interception and tampering by a network-positioned attacker. Versions below 8.6.0 are affected when a CyberArk REST credential manager integration is configured; the client accepts any server certificate without verification, making TLS sessions transparent to a man-in-the-middle. No public exploit code has been identified at time of analysis, and the vulnerability is absent from the CISA KEV catalog, but the high confidentiality and integrity impact on privileged credential data warrants priority remediation in environments relying on CyberArk for SOAR playbook secrets.
Arbitrary code execution in Splunk SOAR (On-premises) versions below 8.6.0 is reachable by any authenticated user regardless of role assignment, via a crafted file path submitted to the REST API. The REST API endpoint neither enforces role-based access control nor restricts the user-supplied path to the intended temporary directory, enabling path traversal (CWE-22) that culminates in code execution on the SOAR server. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the low privilege barrier - any valid account, zero roles required - meaningfully elevates real-world risk in environments where SOAR accounts are broadly provisioned.
Remote code execution in Splunk SOAR versions below 8.6.0 allows unauthenticated remote attackers to execute arbitrary code on the SOAR host by exploiting the Automation Broker's blind trust of client-supplied IP address headers. The Automation Broker accepts a forged source-IP header as proof that a notification endpoint request originates from the local system (CWE-290), bypassing all authentication. Successful exploitation grants full confidentiality, integrity, and availability impact on the SOAR host; no public exploit is identified at time of analysis, but the vendor has released a patch in version 8.6.0.
Unauthenticated remote disclosure of Edge Processor pipeline configurations in Splunk Enterprise 10.4.x exposes potentially sensitive data-processing logic to any network-accessible attacker. The REST API endpoint serving Edge Processor configuration lacks authentication controls (CWE-306), meaning any unauthenticated actor can retrieve pipeline details when the Edge Processor feature is enabled. No public exploit code has been identified at time of analysis, and the flaw is restricted to the 10.4.x branch - prior versions are unaffected.
Search Head Clustering bundle replication in Splunk Enterprise fails to validate bundle filenames or neutralize NUL bytes before constructing file system paths on non-captain cluster members, allowing any authenticated low-privileged user to delete or temporarily overwrite files accessible to the Splunk service account via a crafted REST API request. Affected are Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 running in SHC deployments - standalone instances are not in scope. No public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV; however, vendor patch is available via advisory SVD-2026-0801 and the low privilege barrier makes this a credible insider or stolen-credential threat in SOC environments.
Privilege escalation in Splunk Enterprise allows any authenticated low-privileged user to create or modify scripted lookups through improperly guarded generic transforms configuration endpoints, gaining code execution under the Splunk service account's operating system permissions. Affected versions span four release branches: 9.4.x below 9.4.14, 10.0.x below 10.0.9, 10.2.x below 10.2.6, and 10.4.x below 10.4.2. An attacker holding any valid Splunk account - without requiring the 'admin' or 'power' roles - can abuse this to access all Splunk-indexed data and compromise system integrity and availability. No public exploit or CISA KEV listing has been identified at time of analysis.
Splunk Secure Gateway's failure to validate decoded report notification identifiers enables any authenticated low-privileged user to hijack system-level REST API sessions in Splunk Enterprise, achieving full configuration control and credential theft without requiring admin or power role. Affected versions span multiple Splunk Enterprise branches (9.4.x, 10.0.x, 10.2.x, 10.4.x) and Splunk Secure Gateway branches (3.8.x, 3.9.x, 3.10.x). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, low-privilege attack path and high-impact outcome (C:H/I:H/A:H) make this a realistic internal threat in any multi-tenant or shared Splunk deployment.
Privilege escalation in Splunk Enterprise allows any user holding the schedule_search capability to execute arbitrary SPL commands with system-level privileges on the search head by configuring PDF attachments in the email alert action workflow. The flaw exists because the search scheduler substitutes a system-level authentication context for the alert owner's context during PDF rendering, effectively granting the authenticated user full system access. Affected are all Splunk Enterprise installations across the 9.4, 10.0, 10.2, and 10.4 release branches below the patched versions; no public exploit or CISA KEV listing is identified at time of analysis.
Path traversal in Splunk Enterprise allows low-privileged authenticated users to write dispatch metadata to arbitrary locations on the host filesystem by supplying a crafted search identifier to a REST API endpoint. Affected branches span versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, covering all currently maintained Splunk Enterprise release lines. No public exploit has been identified at time of analysis and the vulnerability is absent from CISA KEV, but the low complexity, network accessibility, and high integrity impact create meaningful risk on unpatched instances, particularly given the potential for filesystem write primitives to be chained into privilege escalation.
Authentication bypass in Splunk Enterprise across multiple supported version branches allows an attacker who has obtained a trusted distributed search private key to forge administrative session tokens entirely over the network. Affected versions span 9.4.x below 9.4.14, 10.0.x below 10.0.9, 10.2.x below 10.2.6, and 10.4.x below 10.4.2. Once a forged token is accepted, the attacker gains full confidentiality, integrity, and availability impact equivalent to an administrator - including access to all indexed data and the ability to disrupt search services. No public exploit or CISA KEV listing exists at time of analysis; this was reported by Cisco, suggesting coordinated disclosure from security research.
Insufficient authorization in Splunk Enterprise's SPL2 module management REST API allows any authenticated low-privileged user - one without the 'admin' or 'power' role - to delete all SPL2 modules across every app and user on the instance. Affected versions are 10.2.x through 10.2.5 and 10.4.x through 10.4.1; versions below 10.2 are unaffected as SPL2 module management did not exist there. The resulting impact is high integrity loss (permanent deletion of exported datasets and functions) and partial service disruption, with no patch-confirmed active exploitation at time of analysis.
Authenticated low-privilege code injection in Splunk Enterprise allows OS command execution on the host system as the Splunk process account. Affected versions span four active release lines (9.4.x, 10.0.x, 10.2.x, 10.4.x), and the root cause is a missing capability check: Splunk Web accepts Splunk Web Manager XML configuration writes without enforcing the edit_manager_xml permission, meaning any authenticated user can plant attacker-controlled content that executes when the Manager page is rendered. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, but the CVSS score of 8.8 (High) and straightforward exploitation path make this a high-priority patching target for Splunk deployments.
Stored cross-site scripting in Splunk Enterprise's Dashboard Studio allows a user holding the 'power' role to persist a crafted workflow action URL that, when triggered by a separate authenticated victim, executes attacker-controlled JavaScript in the victim's browser session. All four actively maintained branches are affected: 10.4.x below 10.4.2, 10.2.x below 10.2.6, 10.0.x below 10.0.9, and 9.4.x below 9.4.14. No public exploit has been identified at time of analysis, and exploitation is constrained by a required internal 'power' role and mandatory victim social engineering, meaningfully limiting the realistic attacker population despite the high impact ratings.
SPL injection via Analytics Workspace in Splunk Enterprise allows an unauthenticated attacker to execute arbitrary Search Processing Language queries under the permissions of a phished authenticated user. Affected across four release trains - 9.4 below 9.4.14, 10.0 below 10.0.9, 10.2 below 10.2.6, and 10.4 below 10.4.2 - the flaw stems from insufficient input validation when Analytics Workspace constructs searches from URL-embedded data. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, though exploitation impact scales directly with the victim user's Splunk role and data access.
SPL injection in Splunk Enterprise exposes all indexed data and compromises search integrity for any low-privileged authenticated user. Specifically, users without the 'admin' or 'power' role can inject Search Processing Language commands into saved-search dispatch requests by supplying malicious time values that Splunk Enterprise fails to validate. Patch versions have been released across all supported branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Reflected SPL injection in Splunk Enterprise's Monitoring Console allows an unauthenticated attacker to execute attacker-controlled Search Processing Language commands under the permissions of a phished authenticated victim. Affected versions span four active release trains: 9.4.x below 9.4.14, 10.0.x below 10.0.9, 10.2.x below 10.2.6, and 10.4.x below 10.4.2. No public exploit or CISA KEV listing exists at time of analysis, though successful exploitation grants full read and write access to all data and actions permitted by the victim's Splunk role.
Stored cross-site scripting in Splunk Enterprise allows a 'power' role user to persist a malicious ui-tour knowledge object that executes arbitrary JavaScript in the browser of any authenticated user who visits an affected Splunk Web page. Affected are all Splunk Enterprise deployments running versions below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, a broad multi-branch footprint reported via Cisco and confirmed by Splunk advisory SVD-2026-0801. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 7.3 rating and high confidentiality and integrity impact scores reflect meaningful lateral risk within an enterprise's Splunk deployment.
SPL injection in Splunk Enterprise's Job Details dashboard enables a low-privileged authenticated attacker to bypass Search Processing Language risky-command safeguards by embedding a malicious search identifier in a crafted dashboard URL and phishing an authenticated victim into opening it. The injected SPL executes under the victim's permissions, potentially exposing all data accessible to that user and compromising search integrity within those bounds. No active exploitation is confirmed and no public exploit code has been identified; a vendor patch is available across all four affected release trains per advisory SVD-2026-0801.
Dashboard Studio in Splunk Enterprise (below versions 9.4.14, 10.0.9, 10.2.6, and 10.4.2) allows a low-privileged 'user'-role account to inject attacker-controlled SPL queries that execute within the authenticated session of a different, potentially higher-privileged victim user. The root cause is Dashboard Studio's failure to consistently enforce app-visibility authorization boundaries before search query options reach the search dispatch layer - a CWE-862 Missing Authorization defect. No public exploit code or active exploitation has been confirmed; a vendor patch is available across all affected branches.
Unauthenticated SPL injection in Splunk Enterprise's nearby-event search feature allows remote attackers to execute arbitrary Search Processing Language queries without authorization across versions 9.4.x, 10.0.x, 10.2.x, and 10.4.x. The root cause is a two-pronged failure: Splunk Web does not consistently escape caller-supplied values when constructing SPL for nearby-event searches, and the embedded report access endpoint accepts those crafted requests without performing the expected authorization check. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the unauthenticated network vector and wide enterprise deployment of Splunk make this a priority patch.
Remote code execution in Splunk Enterprise allows any low-privileged authenticated user to execute arbitrary code by exploiting a missing authorization check in the Federated Search dispatch flow. The vulnerability stems from the platform accepting caller-controlled bundle selection without verifying the fsh_manage capability, meaning any user with basic login access can escalate to full RCE. All four active version branches (9.4.x, 10.0.x, 10.2.x, 10.4.x) are affected below their respective patch thresholds; no public exploit or CISA KEV listing has been identified at time of analysis.
Path traversal in Splunk Enterprise's lookup configuration endpoint allows any authenticated low-privileged user - without admin or power roles - to move arbitrary files readable by the Splunk service account into a user-controlled lookup table on the search head. Affected versions span four active release trains: 10.4.x below 10.4.2, 10.2.x below 10.2.6, 10.0.x below 10.0.9, and 9.4.x below 9.4.14. With a CVSS score of 8.8 and no special configuration required beyond a standard Splunk account, successful exploitation yields full confidentiality, integrity, and availability impact; no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Stored SPL injection in Splunk Enterprise allows an unauthenticated attacker who can reach the management port to register a crafted Deployment Server client identity containing malicious Search Processing Language code, which executes when an administrator opens the Add Data forwarder workflow. All four supported major branches are affected (9.4.x, 10.0.x, 10.2.x, 10.4.x), with vendor-confirmed fixes available. No public exploit has been identified at time of analysis, but successful exploitation yields full confidentiality, integrity, and availability impact on the Splunk platform instance.
Remote code execution in Splunk Enterprise allows any authenticated low-privileged user - one without the 'admin' or 'power' role - to inject and execute arbitrary code on the Splunk platform instance via the Splunk Web Manager Configuration REST API endpoint. The root cause is a missing permission check on the REST API path governing manager configuration writes, meaning Splunk evaluates attacker-supplied configuration values without verifying the caller holds the required role. Exploitation yields full confidentiality, integrity, and availability impact on the Splunk instance; no public exploit has been identified at time of analysis.
Remote code execution in Splunk Enterprise allows any authenticated low-privilege user - one who does not hold the 'admin' or 'power' role - to execute arbitrary code by submitting crafted XML content to the Splunk Web Manager Configuration endpoint. The vulnerability combines two weaknesses: server-side evaluation of manager XML expressions without sufficient input restrictions (CWE-94), and a missing capability check on the configuration route that should gate such access. No public exploit has been identified at time of analysis, but the low attack complexity and low privilege requirement make this a high-priority remediation target across Splunk Enterprise 9.4.x, 10.0.x, 10.2.x, and 10.4.x branches.
Remote code execution in Splunk Enterprise allows any authenticated low-privilege user (without admin or power roles) to upload a malicious knowledge bundle via the REST API and force distributed search to execute it across search peers, achieving full C/I/A compromise. The root cause is a missing authorization check - the REST API endpoint for knowledge bundle uploads does not enforce the required edit_dist_peer capability, and distributed search blindly honors caller-supplied bundle selections. No public exploit or CISA KEV listing has been identified at time of analysis, but the low authentication bar (any valid Splunk account suffices) and network-accessible attack surface make this a high-priority patching target in enterprise environments.
Session material exposure in Splunk Enterprise (versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14) allows an unauthenticated attacker who can view the HTML source of any page that embeds a Splunk report to harvest session credentials and reach the underlying search data with high confidentiality and integrity impact. The flaw stems from the dispatch archive download path failing to enforce the embedded-report authorization boundary, so archived search-job data carries sensitive session material. Rated CVSS 9.4 and reported by Cisco; no public exploit is identified at time of analysis and it is not listed in CISA KEV.
Improper access control in Splunk Enterprise (versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14) allows a party holding only an embedded report token to download the dispatch archive of an embedded report's search job, exposing session material that grants access to sensitive data and the ability to affect platform integrity. The embedded-report authorization flow fails to block dispatch-archive download requests before the archive begins streaming, so the check is effectively bypassed (CWE-284). No public exploit has been identified at time of analysis, but the 9.4 CVSS score and unauthenticated network vector make this a high-priority patch.
Improper access control in Splunk Enterprise (versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14) lets anyone holding an embedded report token download the underlying search job's dispatch archive over the REST API, recover session material, and impersonate the report owner. Because embedded reports are designed to be shared with unauthenticated viewers, an attacker can read all data the owner can access and, if the owner holds the admin role, perform administrative actions. No public exploit is identified at time of analysis, but the CVSS 9.4 rating and unauthenticated network vector make this high priority.
Unauthenticated information disclosure in Splunk Enterprise 10.4.x exposes Prometheus service metrics from the Edge Processor SPL2 Preview sidecar to any network-reachable client. The sidecar's Prometheus metrics endpoint lacks authentication, allowing retrieval of runtime and build metadata without credentials. No public exploit code has been identified at time of analysis, and the vulnerability does not affect Splunk Enterprise versions below 10.4.
Splunk Enterprise for Windows exposes a startup race condition on the management port that allows a low-privileged local user to intercept authentication tokens from Splunk child processes. By pre-binding the management port before the Splunk service initializes - exploiting the absence of exclusive address binding protections on Windows - an attacker captures session tokens that can be replayed to compromise all data and system integrity accessible to the Splunk service account. No public exploit code has been identified and EPSS is 0.12% (3rd percentile), indicating low current exploitation activity; however, the vulnerability is Windows-specific and patch is available from Splunk.
The Data Model Editor in Splunk Enterprise fails to apply SPL safeguards for risky commands when executing base searches for auto-extracted fields, allowing a low-privileged attacker (non-admin, non-power role) to craft a malicious request that executes arbitrary SPL commands under a victim's authenticated session via browser-based phishing. Affected branches span four active release lines - 9.4.x below 9.4.13, 10.0.x below 10.0.8, 10.2.x below 10.2.6, and 10.4.x below 10.4.1 - confirmed by vendor advisory SVD-2026-0801. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor patches are available for all affected branches.
SPL injection via Dataset Explorer in Splunk Enterprise allows an unauthenticated attacker to cause an authenticated victim to execute arbitrary Search Processing Language pipelines under that victim's own privileges. Affected versions span five concurrent release branches - 10.4 below 10.4.2, 10.2 below 10.2.6, 10.0 below 10.0.9, 9.4 below 9.4.14, and 9.3 below 9.3.14 - giving this vulnerability broad reach across common enterprise deployments. No CISA KEV listing and no public exploit code have been identified at time of analysis, but the CVSS 8.8 score, wide deployment footprint, and straightforward phishing delivery mechanism make patching urgent.
Privilege escalation in Splunk Enterprise allows an authenticated user holding the schedule_search capability to execute arbitrary SPL commands at the highest system privilege level and read every credential stored in the credential store. Affected versions span four supported release lines - below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 - meaning a wide swath of unpatched deployments across all current branches are exposed. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the credential store access potential makes this a high-priority patch for any deployment where the schedule_search capability is assigned to non-administrator users.
Missing authorization in the Splunk App for Splunk Observability Cloud exposes a stored Observability Cloud access token to any authenticated Splunk user lacking the admin or power role. Affected versions of Splunk Enterprise (below 10.4.2, 10.2.6, and 10.0.9) ship REST API endpoint handlers in the Observability Cloud integration app that fail to enforce the read_o11y_content capability before proxying requests - and the stored token - to Splunk Observability Cloud. Exploitation gives the low-privileged user full read access to all data visible to that token and limited write access to Observability Cloud content. No public exploit or KEV listing has been identified at time of analysis.
Cross-Site Request Forgery combined with SPL injection in Splunk Enterprise (below 10.4.1, 10.2.5, 10.0.8, 9.4.13) and Splunk Cloud Platform lets an attacker trick a logged-in user holding the list_deployment_server capability into unknowingly executing attacker-controlled Search Processing Language searches as the privileged splunk-system-user, exposing stored credentials and indexed data. The flaw stems from Deployment Server endpoints in Splunk Web accepting unvalidated GET requests without CSRF token checks and failing to neutralize caller input before it reaches an SPL search. No public exploit has been identified at time of analysis and it is not listed in CISA KEV.
Arbitrary file write in Splunk Enterprise (versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, 9.3.14) and Splunk Cloud Platform lets a privileged user with the edit_local_apps and install_apps capabilities abuse the app-installation workflow to write files outside the target app directory into $SPLUNK_HOME/etc/ and its subdirectories. The flaw is a path traversal (CWE-22) that can be leveraged to overwrite Splunk configuration and system files, yielding high confidentiality, integrity, and availability impact. No public exploit identified at time of analysis and it is not listed in CISA KEV.
Authenticated command injection in Splunk AI Toolkit versions below 5.7.4 allows a user with the Splunk admin role to execute arbitrary OS commands on the underlying Splunk Enterprise host. The flaw lives in the btool configuration helper, which builds shell command strings from dynamic parameters with shell interpretation enabled. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.4.2604.3 and 10.2.2510.14) allows remote attackers to create or truncate files on the host via an unauthenticated PostgreSQL sidecar service endpoint. The CVSS 9.8 vector (AV:N/AC:L/PR:N/UI:N) reflects trivial network exploitation, and no public exploit identified at time of analysis, though the missing-auth root cause and Splunk's high-value position in enterprise SOCs makes prompt patching warranted.
Server-side request forgery in Splunk Enterprise (below 10.2.4, 10.0.7, 9.4.12, 9.3.13) and Splunk Cloud Platform lets a low-privileged authenticated user coerce the Dashboard Studio PDF export feature into issuing HTTP requests to arbitrary internal destinations. The flaw stems from a flawed prefix-match on trusted domains plus uncritical redirect-following by the PDF export service. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Remote code execution in Splunk Enterprise, Splunk Cloud Platform, and the Splunk Secure Gateway app allows a low-privileged authenticated user (without 'admin' or 'power' roles) to execute arbitrary Python on the server by abusing unsafe jsonpickle deserialization of App Key Value Store (KV Store) data. CVSS is 8.8 (network, low complexity, low privileges) and the issue is currently rated as no public exploit identified at time of analysis. The flaw is reported by Cisco and disclosed via Splunk advisory SVD-2026-0601.
Splunk MCP Server below version 1.0.3 logs session and authorization tokens in clear text within the `_internal` index, exposing them to any user with access to that index or the high-privilege `mcp_tool_admin` capability. A remote attacker with high privileges can view these tokens via the Splunk search interface, enabling session hijacking and impersonation of other users. No public exploit is identified at time of analysis, and the EPSS score of 0.04% indicates very low near-term exploitation probability.
We need to parse the CVE data and synthesize into the required JSON fields. Let's go through each field. - product_name: 1-3 words. Affected products are Splunk Enterprise and Splunk Cloud Platform. The primary product could be "Splunk Enterprise" as the most common on-prem product, but description lists both. We can say "Splunk Enterprise" or "Splunk Cloud Platform". Since the vulnerability is in the apptemp directory handling and it's a low-privileged user with RCE, I'll pick "Splunk Enterprise" as the core product name. However, "Splunk" alone might be too generic, but allowed 1-3 words. So "Splunk Enterprise" is fine. - summary: 2-3 sentences plain-language, not copy of description. Must start with impact verb. Impact is RCE, so something like "Remote code execution in Splunk Enterprise and Splunk Cloud Platform allows...". Specific: low-privileged user (not admin/power) uploads malicious file to apptemp directory due to improper handling, leading to RCE. Affected versions: Enterprise below 10.2.1, 10.0.5, 9.4.10, 9.3.11; Cloud below various versions. Attacker can execute arbitrary code. EPSS low (0.13%), no KEV, no POC mentioned? Tags don't say POC. SSVC says exploitation none, automatable no, total impact. So not actively exploited. Summary: "Remote code execution in Splunk Enterprise and Splunk Cloud Platform allows low-privileged users without admin/power roles to execute arbitrary code by uploading a malicious file to the $SPLUNK_HOME/var/run/splunk/apptemp directory. Affects Enterprise versions before 9.3.11, 9.4.10, 10.0.5, 10.2.1 and Cloud Platform before respective fixed versions. No public exploit identified at time of analysis." - technical_context: underlying technology/protocol: Splunk apptemp directory is a temporary file storage used during app installation or updates. CWE-377 is Insecure Temporary File handling. The root cause is insufficient isolation: files in apptemp can be manipulated by low-privileged users to achieve RCE. CPEs indicate both Splunk Enterprise and Cloud Platform. Could explain that Splunk uses this directory for app staging, and improper handling of file permissions allows malicious upload to trigger code execution, possibly through app validation or loading mechanisms. Educational. - risk_assessment: CVSS 7.1, vector AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H. So network attack, high complexity, low privileges required, user interaction required, scope unchanged, high impact on CIA. EPSS 0.13% (low probability of exploitation, 33rd percentile). Not in KEV. No POC evidence. SSVC: exploitation none, automatable no, technical impact total. So risk is moderate but not actively exploited. Complexity high and user interaction required reduce real-world risk. But total impact, so if exploited, serious. Compare: CVSS is high severity (7.1) but EPSS suggests low exploitation likelihood. Patches available. Real-world priority: apply patches as part of normal cadence, not emergency. Mention that despite low EPSS, the total impact makes it worth remediating. - affected_products: list products with version ranges. Splunk Enterprise: below 10.2.1, 10.0.5, 9.4.10, 9.3.11. Splunk Cloud Platform: below 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, 9.3.2411.127. Reference to vendor advisory: https://advisory.splunk.com/advisories/SVD-2026-0403. No bullet points. - remediation: action: upgrade to fixed versions. Provide exact versions: Enterprise: 9.3.11, 9.4.10, 10.0.5, 10.2.1; Cloud: 9.3.2411.127, 10.0.2503.13, 10.1.2507.19, 10.2.2510.9, 10.3.2512.5, 10.4.2603.0. Workaround maybe not mentioned. Possibly restrict file upload permissions or restrict access to apptemp directory. But no specific workaround in description. I'll say: "Upgrade Splunk Enterprise to version 9.3.11, 9.4.10, 10.0.5, or 10.2.1, and Splunk Cloud Platform to 9.3.2411.127, 10.0.2503.13, 10.1.2507.19, 10.2.2510.9, 10.3.2512.5, or 10.4.2603.0. As a temporary mitigation if upgrading is not possible, restrict write access to the apptemp directory to trusted roles only, but this may impact app installation functionality. Consult advisory SVD-2026-0403." - exploit_scenario: realistic attack: low-privileged Splunk user (without admin/power) uploads a malicious file to the apptemp directory (which they can access) via a crafted request or through app upload functionality if allowed; the file is then processed by Splunk in a way that leads to code execution, potentially via loading a malicious app or configuration. Attack complexity high due to need to trigger processing. Example: "A low-privileged user authenticates to Splunk Web and uploads a specially crafted file to the apptemp directory via the app import feature. When Splunk processes the temporary file for app installation, the malicious payload executes, giving the attacker remote code execution on the Splunk server." - exploitation_conditions: specific prerequisites from description: "low-privileged user that does not hold the admin or power Splunk roles". So attacker must have any low-privileged role, not power/admin. Also, the user must be able to upload a file to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory. That directory might be writable by all authenticated users? The vulnerability is due to improper handling and insufficient isolation of temporary files. So condition: the Splunk instance must allow file uploads to apptemp by low-privileged users. It may be default. User interaction required (UI:R) could refer to the attacker needing to trick a user into processing? Actually UI:R in CVSS means the attacker must trick a user into taking some action. This might be that the low-privileged user must upload the file, but it's the attacker that is that user. In that case, it's not UI. Wait, CVSS says UI:R, which typically requires that the exploitation requires a user other than the attacker to take action. Could be that the attacker needs to convince a victim (another user) to upload the malicious file? The description says "a low-privileged user could potentially perform a Remote Code Execution by uploading a malicious file". That suggests the attacker is the low-privileged user themselves. So UI:R might be misinterpreted? Alternatively, the upload might be via some UI action that the attacker performs. But CVSS defines UI:R as "the vulnerable component requires user interaction to function. ... the user interaction is required from a user other than the attacker." So if the attacker themselves is the user performing the upload, then it's not UI:R but rather PR:L and no UI. The CVSS vector provided shows UI:R, but given descriptions, maybe the attacker must convince a user with low privileges to upload? Could be both: maybe the attacker can be a low-privileged user, but to trigger the RCE they need to interact with the apptemp directory in a way that involves some UI? Possibly the vulnerability is in the handling of uploaded files during app installation, which might be triggered by the user through UI. I think the vector might be AV:N/AC:H/PR:L/UI:N/..., but they put UI:R. I'll respect the given CVSS vector. So exploitation conditions: attacker must be authenticated as a low-privileged user (non-admin, non-power) and must be able to upload a file to apptemp, but also requires user interaction from another user? Perhaps the attacker uploads a file that is then executed when an admin installs or processes an app. That would be UI:R from the admin. So condition: "Exploitation requires an authenticated low-privileged user (without admin or power roles) to upload a malicious file to the apptemp directory, and a subsequent user action (e.g., by an administrator or automated process) that triggers processing of that file." But let's keep to the description. I'll state: "Requires an authenticated Splunk account with any low-privileged role (not admin or power). The attacker must be able to write files to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory, which may be accessible by default. User interaction is required to trigger the RCE (CVSS UI:R), likely from another user such as an administrator performing an app management action." Also add that it's remote over network. So: "Exploitation requires authenticated access as a low-privileged user (non-admin, non-power) and the ability to upload files to the apptemp directory. No specific non-default configuration is required if the directory is writable; however, the high attack complexity and user interaction requirement imply that the attacker must either trick another user into processing the file or rely on specific workflow." - attack_chain: Based on kill chain: authenticated low-privileged user uploads malicious file to apptemp directory via Splunk Web or API → file is stored in apptemp with insufficient isolation → later, an administrator or cron job processes the file (e.g., during app installation or validation) → the malicious payload executes → attacker achieves remote code execution with Splunk service privileges. So chain: "Authenticate as low-privileged Splunk user → Upload malicious file to apptemp directory via app upload feature → Wait for file to be processed by Splunk (e.g., admin action or scheduled task) → Malicious code executes → Gain RCE on Splunk server." 5 steps. - confidence_notes: Vendor advisory exists (SVD-2026-0403) confirming affected versions and patches. EPSS score is low, no KEV. POC status unknown (not listed). The CVE description is from the advisory. SSVC indicates no exploitation, not automatable, total impact. So confidence: "Vendor-confirmed vulnerability with fixed versions published in Splunk advisory SVD-2026-0403. No evidence of public exploit or active exploitation. Affected version ranges and patch availability are confirmed. The exact mechanism of code execution and preconditions (UI:R) require further analysis." - prevalence: Splunk is a widely used enterprise SIEM and log management platform. It is common in large organizations. So prevalence likely "high". Many enterprise environments run Splunk. So "high". - prevalence_basis: "widely deployed enterprise SIEM and log management solution". - assessed_cvss_vector: I need to provide my own independent CVSS. Given the description, I might adjust. The provided CVSS is 7.1: AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H. Is that reasonable? The attack requires network, low privileges, but also user interaction. However, if the attacker is the low-privileged user and they upload a file and that immediately triggers RCE, then UI:N would be more appropriate. But the description doesn't say what triggers the RCE. Could be that the file is uploaded and then automatically processed by some Splunk internal mechanism without user interaction? The CWE-377 is Insecure Temporary File, but the vulnerability could be that the file is placed and then later processed by a service (like a cron job) that doesn't require user interaction. In that case, UI:N. However, the given vector has UI:R, which I'll respect because it's from Splunk themselves. So my assessed vector might differ. I'll reason: The attack requires the attacker to upload a file, but if the processing is automatic, then UI:N. But high complexity maybe due to file format or timing. I'll lean towards UI:N if the description doesn't mention tricking a user. But let's read: "could potentially perform a Remote Code Execution by uploading a malicious file to the $SPLUNK_HOME/var/run/splunk/apptemp directory due to improper handling". So the act of uploading is the vector. The handling is improper, so the mere upload might cause RCE. That suggests no additional user interaction. So I'd set UI:N. Also, the attack complexity: maybe needs specific file content? High? Might be high if
Arbitrary shell command execution in Splunk Enterprise and Cloud Platform allows authenticated users with the edit_cmd capability to inject commands through the unarchive_cmd parameter in the preview upload endpoint. Affected versions include Splunk Enterprise below 10.2.0, 10.0.4, 9.4.9, and 9.3.10, as well as corresponding Cloud Platform versions. An attacker with high-privilege roles could achieve remote code execution on vulnerable systems, though no patch is currently available.
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or power Splunk roles could cause a Remote Code Execution through an external lookup. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100, a low-privileged user who holds a role that has the ‘edit_user’ capability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through the dashboard PDF generation component. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Partial API key exposure in Splunk On-Call (VictorOps) app versions below 1.0.43 allows any authenticated Splunk user - regardless of role - to read a partially masked VictorOps API key from the App Key Value Store (KV Store). The app fails to fully mask the API key prior to persisting it in a KV Store collection that is readable by low-privileged users who do not hold the 'admin' or 'power' Splunk roles, violating the principle of least-privilege for credential storage. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the CVSS score of 4.3 aligns with the limited, partial credential exposure.
Unauthenticated ReDoS in Splunk Connect for Kafka below version 2.2.7 allows a network-accessible attacker to permanently block a Kafka Connect worker thread by submitting a pathological regular expression via the Kafka Connect REST API, which - when triggered by attacker-supplied or coincident matching event data during timestamp extraction - causes the regex engine to backtrack catastrophically without bound. The practical result is complete stoppage of event delivery for the targeted connector, constituting a targeted denial-of-service against Splunk data ingestion pipelines. No public exploit code or CISA KEV listing exists at time of analysis; the CVSS AC:H rating reflects the two-condition prerequisite, moderating the net risk score to 5.9 Medium despite the unauthenticated network vector.
Splunk Connect for Kafka below version 2.2.7 contains an uncontrolled resource consumption flaw in its HTTP Event Collector retry mechanism, enabling an unauthenticated network attacker who can also manipulate HEC endpoint responses to trigger an infinite retry loop that permanently halts Kafka-to-Splunk event delivery. The vulnerability arises because the connector applies an unbounded default retry count for failed HEC batches rather than a finite limit, causing the connector to stall indefinitely when fed persistent failure responses. No active exploitation has been confirmed - the vulnerability is not in CISA KEV - and no public exploit code has been identified at time of analysis.
Missing authorization in Splunk AI Toolkit below version 6.0.1 allows any authenticated low-privilege user to delete the experiment history belonging to another user via the REST API. The root cause is a sequencing flaw: the Toolkit executes the deletion operation before verifying whether the requesting user holds permission to delete the target experiment, violating the principle of check-before-act. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, a patch is available in version 6.0.1.
Unauthenticated model content injection in Splunk AI Toolkit below 6.0.0 allows an authenticated attacker with model upload privileges to overwrite another user's in-progress model upload by racing concurrent requests to the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The root cause is the toolkit's failure to bind uploaded file content to the specific request that creates the corresponding model lookup entry, enabling a TOCTOU-style substitution. No public exploit code or CISA KEV listing has been identified; the vendor (Splunk) has released a patch in version 6.0.0.
Hard-coded and predictable credentials in Splunk AI Toolkit versions below 6.0.0 expose connected container services to unauthorized access by any low-privileged Splunk user. The toolkit generates or stores credentials for its container integrations using predictable or fixed default values, which are retrievable through the AI Toolkit Connections tab without requiring elevated Splunk roles. No public exploit has been identified at time of analysis, and no CISA KEV listing exists, but a vendor patch (6.0.0) is available per advisory SVD-2026-0808, reported by Cisco.
Unauthenticated exposure of the OpenAPI specification in Cisco Talos Intelligence for Enterprise Security Cloud (versions below 1.0.3) allows any network-accessible user to retrieve the add-on's full REST API documentation via Splunk Web static file paths. The disclosed specification reveals API endpoint structure and the authentication model, enabling reconnaissance that could facilitate targeted follow-on attacks. No active exploitation or public exploit code has been identified at time of analysis.
Cleartext exposure of Zoom meeting passwords in the Splunk SOAR interface affects all deployments running the Zoom app for Splunk SOAR below version 3.2.2. Any authenticated SOAR user holding a role with permission to run actions can invoke the create meeting, update meeting, or update user settings actions and observe meeting passwords and personal meeting ID (PMI) passwords in plaintext within the SOAR UI. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Cleartext credential exposure in Venafi app for Splunk SOAR versions below 2.1.4 allows any authenticated user with action-run permissions to read keystore and private-key passwords directly from the Splunk SOAR user interface. The root cause is that the app's `keystore_password` and `password` parameters in the 'get certificate' action are not flagged as password-type fields, bypassing the SOAR platform's native masking mechanism. No public exploit code identified at time of analysis, and there is no CISA KEV listing; however, the exposed credentials could enable downstream PKI compromise if observed by a malicious insider.
Cleartext exposure of archive passwords in Splunk Attack Analyzer Connector for Splunk SOAR (versions below 2.2.1) allows authenticated users with action-running permissions to view sensitive archive_password values unmasked in the SOAR user interface. The connector's detonate file and detonate url actions fail to mark the archive_password parameter as a password type, causing the SOAR framework to render it in plaintext during and after action execution. No active exploitation has been identified - the CVE carries no CISA KEV listing and no known public exploit code - but insider or compromised-account exposure is straightforward for any SOAR user with the relevant role.
Information disclosure in the RSA SecurID Authentication Manager app for Splunk SOAR (versions below 1.0.5) exposes RSA token serial numbers in cleartext to any authenticated user with action-run permissions. The app's 'enable token' and 'revoke token' actions fail to mark the token_serial parameter as a password field, causing it to render unmasked in the Splunk SOAR user interface. No public exploit has been identified at time of analysis, and exploitation is constrained by the requirement for an existing Splunk SOAR account with action-execution privileges.
Cleartext exposure of archive passwords in Splunk SOAR's Phantom app (versions below 3.8.5) allows authenticated users with action-running permissions to read sensitive credentials directly from the platform's user interface. The deflate item action fails to mark its password parameter as a sensitive field, causing the archive password to be rendered in plaintext in the SOAR UI to any user who invokes the action. Splunk has released a patch in version 3.8.5 per advisory SVD-2026-0806; no public exploit code or CISA KEV listing has been identified at time of analysis.
Cleartext exposure of temporary Active Directory passwords in the MS Graph for Active Directory app for Splunk SOAR (versions below 1.5.2) allows authenticated users with action-run permissions to capture credentials generated during password reset operations, as the temp_password parameter is rendered in plaintext in the SOAR interface rather than being masked. The flaw stems from the app failing to declare the affected parameter as a password type, causing the Splunk SOAR UI to treat it as generic text output. No active exploitation has been confirmed and no public POC is reported; risk is bounded by the requirement for an authenticated internal SOAR account with specific action-run role permissions.
Cleartext exposure of document passwords in the CrowdStrike OAuth API app for Splunk SOAR (versions below 5.1.3) allows any authenticated user with action-running permissions to read sensitive document_password values directly from the Splunk SOAR user interface. The root cause is the app's failure to mark the document_password parameter as a password type in both the detonate file and detonate url actions, meaning the platform's built-in masking mechanism is never invoked. Vendor patch version 5.1.3 has been released and confirmed via Splunk advisory SVD-2026-0806; no public exploit code or active exploitation has been identified at time of analysis.
Information disclosure in the Cisco Webex App for Splunk SOAR (versions below 2.2.1) exposes Webex meeting passwords in cleartext within the SOAR platform interface. Authenticated users holding roles with action-execution permissions who invoke the 'schedule meeting' action can read the plaintext meeting password directly from the UI, because the app's action manifest fails to designate the password parameter as a masked field. No active exploitation has been identified (not in CISA KEV) and no public exploit code is known; real-world impact is bounded by the requirement for existing SOAR action permissions.
Cleartext exposure of a sensitive sample password in the Cisco Secure Malware Analytics App for Splunk SOAR (versions below 2.4.5) allows authenticated users with action-run permissions to read the sample_password parameter value directly from the Splunk SOAR user interface. The root cause is the app's failure to mark the sample_password field as a password type in the detonate file action, meaning the platform never applies its standard masking behavior to that parameter. No public exploit code or active exploitation has been identified; vendor patch is available at version 2.4.5.
Cleartext exposure of temporary passwords in the Azure AD Graph app for Splunk SOAR (versions below 2.5.3) allows authenticated action-runners to read Azure AD reset credentials directly from the SOAR interface. The app's reset password action fails to classify the temp_password parameter as a sensitive field, so Splunk SOAR renders it unmasked in the UI rather than applying its standard password-masking behavior. Vendor patch 2.5.3 is available per Splunk advisory SVD-2026-0806; no public exploit code and no CISA KEV listing identified at time of analysis.
Credential exposure in the AWS IAM App for Splunk SOAR (all versions below 2.1.9) enables any authenticated user holding a role with action-execution permission to view AWS credentials in cleartext directly within the Splunk SOAR user interface. The root cause is the app's failure to designate the credentials action parameter as a password type field (CWE-312), causing the SOAR platform to render it unmasked rather than redacted. No active exploitation (CISA KEV) or public exploit code has been identified; however, because the exposed material consists of AWS access credentials rather than generic application data, the downstream business risk - potential cloud account compromise - substantially exceeds what the CVSS 4.3 Medium score conveys.
Credential exposure in the AD LDAP app for Splunk SOAR (versions below 2.3.8) allows any authenticated user holding an action-execution role to trigger a full connector process environment dump to a persistent plaintext debug log file, disclosing sensitive credentials such as LDAP bind secrets or service account tokens. The CVSS scope-changed vector (S:C) reflects that the exposed credentials extend impact beyond the SOAR platform itself to the underlying Active Directory environment. No public exploit code exists and this vulnerability is not listed in CISA KEV at time of analysis; however, patch version 2.3.8 is available and should be applied promptly given the potential for AD credential theft.
Sensitive Active Directory response data exposure in the AD LDAP App for Splunk SOAR (versions below 2.3.8) allows authenticated users holding action-execution permissions to cause AD directory data to be written to a persistent debug log file. The flaw is rooted in CWE-532 (insertion of sensitive information into log files) and is reachable over the network by any low-privileged SOAR user with the appropriate role. No public exploit code or active exploitation has been identified; Splunk has released a patch at version 2.3.8.
LDAP injection in the AD LDAP app for Splunk SOAR (versions below 2.3.8) allows authenticated low-privileged users to manipulate Active Directory queries, exposing account enumeration, sensitive attribute disclosure, and unintended modification of AD objects. Exploitation requires only a role with 'run actions' permission within Splunk SOAR - no elevated SOAR admin rights needed. Splunk has released a patch (version 2.3.8); no public exploit code or CISA KEV listing has been identified at time of analysis.
The Nmap Scanner connector for Splunk SOAR (versions prior to 3.0.15) permits privileged users to bypass Safe Mode playbook restrictions by exploiting a manifest miscategorization that marks the scan network action as read-only despite its accepting NSE script parameters capable of write operations and command execution on target systems. Users holding roles that allow editing, creating, or running playbooks can leverage this gap to run arbitrary Nmap Scripting Engine scripts against networked targets through SOAR automation - a meaningful privilege escalation given SOAR platforms typically have broad network reach. No public exploit has been identified at time of analysis, and a vendor patch is available via Splunk advisory SVD-2026-0806.
FireAMP connector versions below 2.1.15 for Splunk SOAR allow authenticated playbook editors to bypass Safe Mode restrictions by invoking the add listitem action, which the connector manifest incorrectly classifies as read-only despite it performing write operations on file lists. Exploitation requires a high-privilege role (playbook edit/create/run), limiting the attack surface to trusted internal SOAR users. No public exploit code exists and this vulnerability has not been identified in CISA KEV, consistent with its low CVSS score of 2.7.
Splunk SOAR versions below 8.6.0 expose tenant names and identifiers to authenticated users whose roles restrict them to a subset of tenants, due to a REST API authorization enforcement gap. In multi-tenant deployments, a low-privileged user can enumerate out-of-scope tenant metadata - names and identifiers - without triggering any access control check. No active exploitation or public exploit code has been identified; the CVSS score of 4.3 (Medium) reflects limited confidentiality impact with no integrity or availability consequence.
Path traversal in Splunk SOAR below 8.6.0 enables users holding the OnPrem Broker role to write files to arbitrary locations outside the designated Automation Broker log directory. The flaw stems from the log upload endpoint accepting crafted filenames without adequate sanitization, allowing directory traversal sequences to escape the intended write boundary. No public exploit has been identified and no active exploitation is confirmed; the CVSS score of 2.7 (Low) accurately reflects the high privilege prerequisite and the limited, integrity-only impact.
Splunk SOAR versions below 8.6.0 expose a missing authorization flaw in the Playbook History feature that allows authenticated users holding the `playbooks:view` permission to read metadata about playbook repositories they are not explicitly authorized to access. The Playbook History endpoint omits repository-level permission checks before returning revision metadata, enabling unauthorized information disclosure within role-segregated SOAR deployments. No active exploitation has been confirmed - there is no CISA KEV listing and no public exploit code has been identified - and the CVSS base score of 2.7 reflects the high-privilege prerequisite and narrow confidentiality-only impact scope.
Stored XSS in Splunk SOAR below 8.6.0 enables an authenticated 'Incident Commander' role user to inject JavaScript into a note, which executes in the browser of any user who subsequently opens it. The flaw stems from unsanitized HTML rendering triggered by a note format change, meaning content stored safely in one format becomes executable in another. No public exploit code exists and the vulnerability is absent from CISA KEV; however, successful exploitation could compromise victim session integrity within the SOAR platform.
Session token disclosure in Splunk SOAR versions below 8.6.0 enables any authenticated account holder to recover session tokens belonging to other users by manipulating REST API filters on the playbook run endpoint. Because Splunk SOAR fails to block filter predicates from matching against values that are otherwise suppressed in API responses, an attacker with a low-privilege account can systematically extract credentials granting full access to any targeted user's data within the platform. Splunk has released version 8.6.0 as a fix; no public exploit has been identified at time of analysis, but the low attack complexity elevates urgency for organizations where multiple users share a SOAR instance.
Log injection in @logtape/syslog allows network-accessible attackers to forge arbitrary syslog records in downstream collectors such as rsyslog, Splunk, and Elastic Stack. The escapeStructuredDataValue() function omits C0 control character escaping, so a literal newline embedded in a log property value terminates the current RFC 6587 TCP syslog frame and begins a new one; if the attacker-supplied bytes constitute a valid RFC 5424 header, the downstream collector accepts them as a separate, authentic-looking record. A second injection path exists through unvalidated SD-NAME keys, which can prematurely close structured-data elements. Both paths require the non-default SyslogSinkOptions.includeStructuredData: true setting. Publicly available proof-of-concept code exists; no CISA KEV listing at time of analysis.
Operating-system command execution in the Splunk MCP Server app (all versions below 1.2.1) lets a user already holding the Splunk 'admin' role run arbitrary commands on the underlying host by abusing unsafe deserialization in the credential-management component. Because the app trusts stored data and deserializes it without verifying the object type, a privileged Splunk user can escalate from application-level administration to full host compromise. No public exploit identified at time of analysis, and it is not listed in CISA KEV; a vendor patch is available.
Certificate validation bypass in Splunk Connect for Kafka below version 2.2.7 allows a network-positioned unauthenticated attacker to intercept and modify event data in transit to Splunk Enterprise's HTTP Event Collector when Kerberos authentication is configured. The Kerberos code path fails to apply the connector's configured TLS certificate validation options when constructing the HTTP client, effectively negating transport security despite HEC's TLS configuration. No active exploitation has been identified (not in CISA KEV), but the confidentiality and integrity impact on Splunk-ingested telemetry data is high.
Unauthenticated access to the Kafka Connect REST API in Splunk Connect for Kafka versions below 2.2.7 enables an SSRF-class attack that reconfigures the HTTP Event Collector destination to an attacker-controlled endpoint, resulting in theft of HEC authentication credentials and partial manipulation of event delivery to Splunk Enterprise. The connector's HEC endpoint validation does not enforce secure transport by default, meaning a non-TLS HTTP destination can be substituted without any authentication. No public exploit has been identified at time of analysis, but the attack requires no privileges and trivially low complexity, making any deployment with a network-exposed Kafka Connect REST API immediately actionable.
Splunk AI Toolkit before version 6.0.1 allows authenticated users holding the built-in 'power' role to modify app-provided scheduled searches, which execute SPL under the permissions of the search owner rather than the modifying user. By injecting arbitrary SPL into such searches, a 'power' role user can access all data visible to the search owner and alter system integrity - effectively escalating privileges beyond their authorization level. No public exploit code or active exploitation has been identified at time of analysis.
Unauthorized cross-user data access and deletion in Splunk AI Toolkit below 6.0.0 allows any authenticated user holding the 'power' Splunk role to read and destroy experiment history records belonging to other users. The root cause is CWE-639 (IDOR): the toolkit fails to preserve a trusted experiment scope boundary when processing caller-controlled query values, enabling horizontal privilege escalation across all experiment history without touching admin-level permissions. No active exploitation or public exploit code has been identified at time of analysis; a vendor-released patch (6.0.0) is available per Splunk advisory SVD-2026-0808.
Improper access control in Splunk AI Toolkit versions below 6.0.0 allows an authenticated user holding the schedule_search capability to deserialize arbitrary model files by invoking the apply search command via a scheduled search. Because the toolkit does not designate apply as a risky command, Splunk's built-in risky-command access controls are never triggered, enabling privilege escalation beyond what the role should permit. A vendor-released patch exists (version 6.0.0); no public exploit or CISA KEV listing has been identified at time of analysis.
Arbitrary code execution in Splunk AI Toolkit below 6.0.0 is achievable by any user holding the Splunk 'power' role, through loading a crafted model file that embeds malicious pickle payloads inside sparse matrix data. The toolkit's model codec deserializes this data without sanitizing or restricting the embedded pickle content, granting the attacker code execution as the Splunk server process. No public exploit or CISA KEV listing has been identified at time of analysis, but the RCE impact with a low-privilege network vector makes this a high-priority patch target for any Splunk deployment running the AI or Machine Learning Toolkit.
Missing authorization checks across multiple REST API handlers in Splunk AI Toolkit versions below 6.0.0 allow any low-privileged authenticated Splunk user - one who holds neither the 'admin' nor 'power' role - to start, stop, and reconfigure containers and to read or modify sensitive connection and configuration data. The vulnerability stems from CWE-862 (Missing Authorization), where the REST endpoints simply omit role-based access enforcement rather than incorrectly implementing it. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the low attack complexity and the fact that it was reported by Cisco make it a credible near-term target.
Privilege escalation in Splunk AI Toolkit before 6.0.0 allows any authenticated low-privileged user to operate with system-level permissions by exploiting a session key substitution flaw in the Agent Run History handler. The handler unconditionally replaces the caller's session key with a system authentication token before executing searches, completely bypassing Splunk's role-based access controls that gate elevated operations behind 'admin' or 'power' roles. This grants unauthorized read access to all indexed data, cross-user search job enumeration and deletion, and write-level system integrity impact - no public exploit has been identified at time of analysis, but the low exploitation complexity and clear mechanism description make this a high-priority patching target for Splunk enterprise deployments.
Server-Side Request Forgery (SSRF) in Cisco Talos Intelligence for Enterprise Security Cloud (versions below 1.0.3) allows an authenticated Splunk user holding the get_talos_enrichment capability to redirect the instance's outbound authenticated management requests to an attacker-controlled server, exposing Splunk management tokens. Successful exploitation grants the attacker full control over the Splunk instance, compromising the confidentiality, integrity, and availability of all data and configurations within it. No public exploit code or CISA KEV listing has been identified at time of analysis, but the patch is available and the CVSS score of 8.8 reflects the severity of token theft as a post-exploitation path.
Privilege escalation in Splunk Enterprise Security below 8.6.1 enables authenticated users holding the ess_analyst role to modify UEBA search macros that are subsequently executed by scheduled searches running under administrator permissions. The flaw stems from misconfigured UEBA app metadata that incorrectly grants analyst-tier write access to macros intended to be restricted to administrators, resulting in unauthorized access to all Splunk-indexed data and potential system integrity violations. No public exploit or CISA KEV listing exists at time of analysis, though the low barrier - any ess_analyst account - makes insider threat and compromised analyst credential scenarios credible attack paths.
SPL injection in Splunk Enterprise Security versions below 8.6.1 allows low-privileged authenticated users holding the mc_investigation_read capability to inject Search Processing Language through Analyst Queue search filter field names, gaining access to data and system integrity controls available to scheduled search contexts beyond their authorized scope. The root cause is absent validation of filter field names before inclusion in SPL queries - analogous to SQL injection but within Splunk's proprietary query language. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the CVSS 8.1 High score reflects meaningful confidentiality and integrity exposure for any account holding the relevant capability.
Improper TLS certificate validation in Splunk SOAR's CyberArk REST client exposes all credential vault traffic to interception and tampering by a network-positioned attacker. Versions below 8.6.0 are affected when a CyberArk REST credential manager integration is configured; the client accepts any server certificate without verification, making TLS sessions transparent to a man-in-the-middle. No public exploit code has been identified at time of analysis, and the vulnerability is absent from the CISA KEV catalog, but the high confidentiality and integrity impact on privileged credential data warrants priority remediation in environments relying on CyberArk for SOAR playbook secrets.
Arbitrary code execution in Splunk SOAR (On-premises) versions below 8.6.0 is reachable by any authenticated user regardless of role assignment, via a crafted file path submitted to the REST API. The REST API endpoint neither enforces role-based access control nor restricts the user-supplied path to the intended temporary directory, enabling path traversal (CWE-22) that culminates in code execution on the SOAR server. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the low privilege barrier - any valid account, zero roles required - meaningfully elevates real-world risk in environments where SOAR accounts are broadly provisioned.
Remote code execution in Splunk SOAR versions below 8.6.0 allows unauthenticated remote attackers to execute arbitrary code on the SOAR host by exploiting the Automation Broker's blind trust of client-supplied IP address headers. The Automation Broker accepts a forged source-IP header as proof that a notification endpoint request originates from the local system (CWE-290), bypassing all authentication. Successful exploitation grants full confidentiality, integrity, and availability impact on the SOAR host; no public exploit is identified at time of analysis, but the vendor has released a patch in version 8.6.0.
Unauthenticated remote disclosure of Edge Processor pipeline configurations in Splunk Enterprise 10.4.x exposes potentially sensitive data-processing logic to any network-accessible attacker. The REST API endpoint serving Edge Processor configuration lacks authentication controls (CWE-306), meaning any unauthenticated actor can retrieve pipeline details when the Edge Processor feature is enabled. No public exploit code has been identified at time of analysis, and the flaw is restricted to the 10.4.x branch - prior versions are unaffected.
Search Head Clustering bundle replication in Splunk Enterprise fails to validate bundle filenames or neutralize NUL bytes before constructing file system paths on non-captain cluster members, allowing any authenticated low-privileged user to delete or temporarily overwrite files accessible to the Splunk service account via a crafted REST API request. Affected are Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 running in SHC deployments - standalone instances are not in scope. No public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV; however, vendor patch is available via advisory SVD-2026-0801 and the low privilege barrier makes this a credible insider or stolen-credential threat in SOC environments.
Privilege escalation in Splunk Enterprise allows any authenticated low-privileged user to create or modify scripted lookups through improperly guarded generic transforms configuration endpoints, gaining code execution under the Splunk service account's operating system permissions. Affected versions span four release branches: 9.4.x below 9.4.14, 10.0.x below 10.0.9, 10.2.x below 10.2.6, and 10.4.x below 10.4.2. An attacker holding any valid Splunk account - without requiring the 'admin' or 'power' roles - can abuse this to access all Splunk-indexed data and compromise system integrity and availability. No public exploit or CISA KEV listing has been identified at time of analysis.
Splunk Secure Gateway's failure to validate decoded report notification identifiers enables any authenticated low-privileged user to hijack system-level REST API sessions in Splunk Enterprise, achieving full configuration control and credential theft without requiring admin or power role. Affected versions span multiple Splunk Enterprise branches (9.4.x, 10.0.x, 10.2.x, 10.4.x) and Splunk Secure Gateway branches (3.8.x, 3.9.x, 3.10.x). No public exploit code or CISA KEV listing has been identified at time of analysis, but the low-complexity, low-privilege attack path and high-impact outcome (C:H/I:H/A:H) make this a realistic internal threat in any multi-tenant or shared Splunk deployment.
Privilege escalation in Splunk Enterprise allows any user holding the schedule_search capability to execute arbitrary SPL commands with system-level privileges on the search head by configuring PDF attachments in the email alert action workflow. The flaw exists because the search scheduler substitutes a system-level authentication context for the alert owner's context during PDF rendering, effectively granting the authenticated user full system access. Affected are all Splunk Enterprise installations across the 9.4, 10.0, 10.2, and 10.4 release branches below the patched versions; no public exploit or CISA KEV listing is identified at time of analysis.
Path traversal in Splunk Enterprise allows low-privileged authenticated users to write dispatch metadata to arbitrary locations on the host filesystem by supplying a crafted search identifier to a REST API endpoint. Affected branches span versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, covering all currently maintained Splunk Enterprise release lines. No public exploit has been identified at time of analysis and the vulnerability is absent from CISA KEV, but the low complexity, network accessibility, and high integrity impact create meaningful risk on unpatched instances, particularly given the potential for filesystem write primitives to be chained into privilege escalation.
Authentication bypass in Splunk Enterprise across multiple supported version branches allows an attacker who has obtained a trusted distributed search private key to forge administrative session tokens entirely over the network. Affected versions span 9.4.x below 9.4.14, 10.0.x below 10.0.9, 10.2.x below 10.2.6, and 10.4.x below 10.4.2. Once a forged token is accepted, the attacker gains full confidentiality, integrity, and availability impact equivalent to an administrator - including access to all indexed data and the ability to disrupt search services. No public exploit or CISA KEV listing exists at time of analysis; this was reported by Cisco, suggesting coordinated disclosure from security research.
Insufficient authorization in Splunk Enterprise's SPL2 module management REST API allows any authenticated low-privileged user - one without the 'admin' or 'power' role - to delete all SPL2 modules across every app and user on the instance. Affected versions are 10.2.x through 10.2.5 and 10.4.x through 10.4.1; versions below 10.2 are unaffected as SPL2 module management did not exist there. The resulting impact is high integrity loss (permanent deletion of exported datasets and functions) and partial service disruption, with no patch-confirmed active exploitation at time of analysis.
Authenticated low-privilege code injection in Splunk Enterprise allows OS command execution on the host system as the Splunk process account. Affected versions span four active release lines (9.4.x, 10.0.x, 10.2.x, 10.4.x), and the root cause is a missing capability check: Splunk Web accepts Splunk Web Manager XML configuration writes without enforcing the edit_manager_xml permission, meaning any authenticated user can plant attacker-controlled content that executes when the Manager page is rendered. No active exploitation is confirmed in CISA KEV, and no public exploit code has been identified at time of analysis, but the CVSS score of 8.8 (High) and straightforward exploitation path make this a high-priority patching target for Splunk deployments.
Stored cross-site scripting in Splunk Enterprise's Dashboard Studio allows a user holding the 'power' role to persist a crafted workflow action URL that, when triggered by a separate authenticated victim, executes attacker-controlled JavaScript in the victim's browser session. All four actively maintained branches are affected: 10.4.x below 10.4.2, 10.2.x below 10.2.6, 10.0.x below 10.0.9, and 9.4.x below 9.4.14. No public exploit has been identified at time of analysis, and exploitation is constrained by a required internal 'power' role and mandatory victim social engineering, meaningfully limiting the realistic attacker population despite the high impact ratings.
SPL injection via Analytics Workspace in Splunk Enterprise allows an unauthenticated attacker to execute arbitrary Search Processing Language queries under the permissions of a phished authenticated user. Affected across four release trains - 9.4 below 9.4.14, 10.0 below 10.0.9, 10.2 below 10.2.6, and 10.4 below 10.4.2 - the flaw stems from insufficient input validation when Analytics Workspace constructs searches from URL-embedded data. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, though exploitation impact scales directly with the victim user's Splunk role and data access.
SPL injection in Splunk Enterprise exposes all indexed data and compromises search integrity for any low-privileged authenticated user. Specifically, users without the 'admin' or 'power' role can inject Search Processing Language commands into saved-search dispatch requests by supplying malicious time values that Splunk Enterprise fails to validate. Patch versions have been released across all supported branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Reflected SPL injection in Splunk Enterprise's Monitoring Console allows an unauthenticated attacker to execute attacker-controlled Search Processing Language commands under the permissions of a phished authenticated victim. Affected versions span four active release trains: 9.4.x below 9.4.14, 10.0.x below 10.0.9, 10.2.x below 10.2.6, and 10.4.x below 10.4.2. No public exploit or CISA KEV listing exists at time of analysis, though successful exploitation grants full read and write access to all data and actions permitted by the victim's Splunk role.
Stored cross-site scripting in Splunk Enterprise allows a 'power' role user to persist a malicious ui-tour knowledge object that executes arbitrary JavaScript in the browser of any authenticated user who visits an affected Splunk Web page. Affected are all Splunk Enterprise deployments running versions below 10.4.2, 10.2.6, 10.0.9, or 9.4.14, a broad multi-branch footprint reported via Cisco and confirmed by Splunk advisory SVD-2026-0801. No public exploit code or CISA KEV listing has been identified at time of analysis, but the CVSS 7.3 rating and high confidentiality and integrity impact scores reflect meaningful lateral risk within an enterprise's Splunk deployment.
SPL injection in Splunk Enterprise's Job Details dashboard enables a low-privileged authenticated attacker to bypass Search Processing Language risky-command safeguards by embedding a malicious search identifier in a crafted dashboard URL and phishing an authenticated victim into opening it. The injected SPL executes under the victim's permissions, potentially exposing all data accessible to that user and compromising search integrity within those bounds. No active exploitation is confirmed and no public exploit code has been identified; a vendor patch is available across all four affected release trains per advisory SVD-2026-0801.
Dashboard Studio in Splunk Enterprise (below versions 9.4.14, 10.0.9, 10.2.6, and 10.4.2) allows a low-privileged 'user'-role account to inject attacker-controlled SPL queries that execute within the authenticated session of a different, potentially higher-privileged victim user. The root cause is Dashboard Studio's failure to consistently enforce app-visibility authorization boundaries before search query options reach the search dispatch layer - a CWE-862 Missing Authorization defect. No public exploit code or active exploitation has been confirmed; a vendor patch is available across all affected branches.
Unauthenticated SPL injection in Splunk Enterprise's nearby-event search feature allows remote attackers to execute arbitrary Search Processing Language queries without authorization across versions 9.4.x, 10.0.x, 10.2.x, and 10.4.x. The root cause is a two-pronged failure: Splunk Web does not consistently escape caller-supplied values when constructing SPL for nearby-event searches, and the embedded report access endpoint accepts those crafted requests without performing the expected authorization check. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the unauthenticated network vector and wide enterprise deployment of Splunk make this a priority patch.
Remote code execution in Splunk Enterprise allows any low-privileged authenticated user to execute arbitrary code by exploiting a missing authorization check in the Federated Search dispatch flow. The vulnerability stems from the platform accepting caller-controlled bundle selection without verifying the fsh_manage capability, meaning any user with basic login access can escalate to full RCE. All four active version branches (9.4.x, 10.0.x, 10.2.x, 10.4.x) are affected below their respective patch thresholds; no public exploit or CISA KEV listing has been identified at time of analysis.
Path traversal in Splunk Enterprise's lookup configuration endpoint allows any authenticated low-privileged user - without admin or power roles - to move arbitrary files readable by the Splunk service account into a user-controlled lookup table on the search head. Affected versions span four active release trains: 10.4.x below 10.4.2, 10.2.x below 10.2.6, 10.0.x below 10.0.9, and 9.4.x below 9.4.14. With a CVSS score of 8.8 and no special configuration required beyond a standard Splunk account, successful exploitation yields full confidentiality, integrity, and availability impact; no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Stored SPL injection in Splunk Enterprise allows an unauthenticated attacker who can reach the management port to register a crafted Deployment Server client identity containing malicious Search Processing Language code, which executes when an administrator opens the Add Data forwarder workflow. All four supported major branches are affected (9.4.x, 10.0.x, 10.2.x, 10.4.x), with vendor-confirmed fixes available. No public exploit has been identified at time of analysis, but successful exploitation yields full confidentiality, integrity, and availability impact on the Splunk platform instance.
Remote code execution in Splunk Enterprise allows any authenticated low-privileged user - one without the 'admin' or 'power' role - to inject and execute arbitrary code on the Splunk platform instance via the Splunk Web Manager Configuration REST API endpoint. The root cause is a missing permission check on the REST API path governing manager configuration writes, meaning Splunk evaluates attacker-supplied configuration values without verifying the caller holds the required role. Exploitation yields full confidentiality, integrity, and availability impact on the Splunk instance; no public exploit has been identified at time of analysis.
Remote code execution in Splunk Enterprise allows any authenticated low-privilege user - one who does not hold the 'admin' or 'power' role - to execute arbitrary code by submitting crafted XML content to the Splunk Web Manager Configuration endpoint. The vulnerability combines two weaknesses: server-side evaluation of manager XML expressions without sufficient input restrictions (CWE-94), and a missing capability check on the configuration route that should gate such access. No public exploit has been identified at time of analysis, but the low attack complexity and low privilege requirement make this a high-priority remediation target across Splunk Enterprise 9.4.x, 10.0.x, 10.2.x, and 10.4.x branches.
Remote code execution in Splunk Enterprise allows any authenticated low-privilege user (without admin or power roles) to upload a malicious knowledge bundle via the REST API and force distributed search to execute it across search peers, achieving full C/I/A compromise. The root cause is a missing authorization check - the REST API endpoint for knowledge bundle uploads does not enforce the required edit_dist_peer capability, and distributed search blindly honors caller-supplied bundle selections. No public exploit or CISA KEV listing has been identified at time of analysis, but the low authentication bar (any valid Splunk account suffices) and network-accessible attack surface make this a high-priority patching target in enterprise environments.
Session material exposure in Splunk Enterprise (versions below 10.4.1, 10.2.6, 10.0.9, and 9.4.14) allows an unauthenticated attacker who can view the HTML source of any page that embeds a Splunk report to harvest session credentials and reach the underlying search data with high confidentiality and integrity impact. The flaw stems from the dispatch archive download path failing to enforce the embedded-report authorization boundary, so archived search-job data carries sensitive session material. Rated CVSS 9.4 and reported by Cisco; no public exploit is identified at time of analysis and it is not listed in CISA KEV.
Improper access control in Splunk Enterprise (versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14) allows a party holding only an embedded report token to download the dispatch archive of an embedded report's search job, exposing session material that grants access to sensitive data and the ability to affect platform integrity. The embedded-report authorization flow fails to block dispatch-archive download requests before the archive begins streaming, so the check is effectively bypassed (CWE-284). No public exploit has been identified at time of analysis, but the 9.4 CVSS score and unauthenticated network vector make this a high-priority patch.
Improper access control in Splunk Enterprise (versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14) lets anyone holding an embedded report token download the underlying search job's dispatch archive over the REST API, recover session material, and impersonate the report owner. Because embedded reports are designed to be shared with unauthenticated viewers, an attacker can read all data the owner can access and, if the owner holds the admin role, perform administrative actions. No public exploit is identified at time of analysis, but the CVSS 9.4 rating and unauthenticated network vector make this high priority.
Unauthenticated information disclosure in Splunk Enterprise 10.4.x exposes Prometheus service metrics from the Edge Processor SPL2 Preview sidecar to any network-reachable client. The sidecar's Prometheus metrics endpoint lacks authentication, allowing retrieval of runtime and build metadata without credentials. No public exploit code has been identified at time of analysis, and the vulnerability does not affect Splunk Enterprise versions below 10.4.
Splunk Enterprise for Windows exposes a startup race condition on the management port that allows a low-privileged local user to intercept authentication tokens from Splunk child processes. By pre-binding the management port before the Splunk service initializes - exploiting the absence of exclusive address binding protections on Windows - an attacker captures session tokens that can be replayed to compromise all data and system integrity accessible to the Splunk service account. No public exploit code has been identified and EPSS is 0.12% (3rd percentile), indicating low current exploitation activity; however, the vulnerability is Windows-specific and patch is available from Splunk.
The Data Model Editor in Splunk Enterprise fails to apply SPL safeguards for risky commands when executing base searches for auto-extracted fields, allowing a low-privileged attacker (non-admin, non-power role) to craft a malicious request that executes arbitrary SPL commands under a victim's authenticated session via browser-based phishing. Affected branches span four active release lines - 9.4.x below 9.4.13, 10.0.x below 10.0.8, 10.2.x below 10.2.6, and 10.4.x below 10.4.1 - confirmed by vendor advisory SVD-2026-0801. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor patches are available for all affected branches.
SPL injection via Dataset Explorer in Splunk Enterprise allows an unauthenticated attacker to cause an authenticated victim to execute arbitrary Search Processing Language pipelines under that victim's own privileges. Affected versions span five concurrent release branches - 10.4 below 10.4.2, 10.2 below 10.2.6, 10.0 below 10.0.9, 9.4 below 9.4.14, and 9.3 below 9.3.14 - giving this vulnerability broad reach across common enterprise deployments. No CISA KEV listing and no public exploit code have been identified at time of analysis, but the CVSS 8.8 score, wide deployment footprint, and straightforward phishing delivery mechanism make patching urgent.
Privilege escalation in Splunk Enterprise allows an authenticated user holding the schedule_search capability to execute arbitrary SPL commands at the highest system privilege level and read every credential stored in the credential store. Affected versions span four supported release lines - below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 - meaning a wide swath of unpatched deployments across all current branches are exposed. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the credential store access potential makes this a high-priority patch for any deployment where the schedule_search capability is assigned to non-administrator users.
Missing authorization in the Splunk App for Splunk Observability Cloud exposes a stored Observability Cloud access token to any authenticated Splunk user lacking the admin or power role. Affected versions of Splunk Enterprise (below 10.4.2, 10.2.6, and 10.0.9) ship REST API endpoint handlers in the Observability Cloud integration app that fail to enforce the read_o11y_content capability before proxying requests - and the stored token - to Splunk Observability Cloud. Exploitation gives the low-privileged user full read access to all data visible to that token and limited write access to Observability Cloud content. No public exploit or KEV listing has been identified at time of analysis.
Cross-Site Request Forgery combined with SPL injection in Splunk Enterprise (below 10.4.1, 10.2.5, 10.0.8, 9.4.13) and Splunk Cloud Platform lets an attacker trick a logged-in user holding the list_deployment_server capability into unknowingly executing attacker-controlled Search Processing Language searches as the privileged splunk-system-user, exposing stored credentials and indexed data. The flaw stems from Deployment Server endpoints in Splunk Web accepting unvalidated GET requests without CSRF token checks and failing to neutralize caller input before it reaches an SPL search. No public exploit has been identified at time of analysis and it is not listed in CISA KEV.
Arbitrary file write in Splunk Enterprise (versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, 9.3.14) and Splunk Cloud Platform lets a privileged user with the edit_local_apps and install_apps capabilities abuse the app-installation workflow to write files outside the target app directory into $SPLUNK_HOME/etc/ and its subdirectories. The flaw is a path traversal (CWE-22) that can be leveraged to overwrite Splunk configuration and system files, yielding high confidentiality, integrity, and availability impact. No public exploit identified at time of analysis and it is not listed in CISA KEV.
Authenticated command injection in Splunk AI Toolkit versions below 5.7.4 allows a user with the Splunk admin role to execute arbitrary OS commands on the underlying Splunk Enterprise host. The flaw lives in the btool configuration helper, which builds shell command strings from dynamic parameters with shell interpretation enabled. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.4.2604.3 and 10.2.2510.14) allows remote attackers to create or truncate files on the host via an unauthenticated PostgreSQL sidecar service endpoint. The CVSS 9.8 vector (AV:N/AC:L/PR:N/UI:N) reflects trivial network exploitation, and no public exploit identified at time of analysis, though the missing-auth root cause and Splunk's high-value position in enterprise SOCs makes prompt patching warranted.
Server-side request forgery in Splunk Enterprise (below 10.2.4, 10.0.7, 9.4.12, 9.3.13) and Splunk Cloud Platform lets a low-privileged authenticated user coerce the Dashboard Studio PDF export feature into issuing HTTP requests to arbitrary internal destinations. The flaw stems from a flawed prefix-match on trusted domains plus uncritical redirect-following by the PDF export service. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Remote code execution in Splunk Enterprise, Splunk Cloud Platform, and the Splunk Secure Gateway app allows a low-privileged authenticated user (without 'admin' or 'power' roles) to execute arbitrary Python on the server by abusing unsafe jsonpickle deserialization of App Key Value Store (KV Store) data. CVSS is 8.8 (network, low complexity, low privileges) and the issue is currently rated as no public exploit identified at time of analysis. The flaw is reported by Cisco and disclosed via Splunk advisory SVD-2026-0601.
Splunk MCP Server below version 1.0.3 logs session and authorization tokens in clear text within the `_internal` index, exposing them to any user with access to that index or the high-privilege `mcp_tool_admin` capability. A remote attacker with high privileges can view these tokens via the Splunk search interface, enabling session hijacking and impersonation of other users. No public exploit is identified at time of analysis, and the EPSS score of 0.04% indicates very low near-term exploitation probability.
We need to parse the CVE data and synthesize into the required JSON fields. Let's go through each field. - product_name: 1-3 words. Affected products are Splunk Enterprise and Splunk Cloud Platform. The primary product could be "Splunk Enterprise" as the most common on-prem product, but description lists both. We can say "Splunk Enterprise" or "Splunk Cloud Platform". Since the vulnerability is in the apptemp directory handling and it's a low-privileged user with RCE, I'll pick "Splunk Enterprise" as the core product name. However, "Splunk" alone might be too generic, but allowed 1-3 words. So "Splunk Enterprise" is fine. - summary: 2-3 sentences plain-language, not copy of description. Must start with impact verb. Impact is RCE, so something like "Remote code execution in Splunk Enterprise and Splunk Cloud Platform allows...". Specific: low-privileged user (not admin/power) uploads malicious file to apptemp directory due to improper handling, leading to RCE. Affected versions: Enterprise below 10.2.1, 10.0.5, 9.4.10, 9.3.11; Cloud below various versions. Attacker can execute arbitrary code. EPSS low (0.13%), no KEV, no POC mentioned? Tags don't say POC. SSVC says exploitation none, automatable no, total impact. So not actively exploited. Summary: "Remote code execution in Splunk Enterprise and Splunk Cloud Platform allows low-privileged users without admin/power roles to execute arbitrary code by uploading a malicious file to the $SPLUNK_HOME/var/run/splunk/apptemp directory. Affects Enterprise versions before 9.3.11, 9.4.10, 10.0.5, 10.2.1 and Cloud Platform before respective fixed versions. No public exploit identified at time of analysis." - technical_context: underlying technology/protocol: Splunk apptemp directory is a temporary file storage used during app installation or updates. CWE-377 is Insecure Temporary File handling. The root cause is insufficient isolation: files in apptemp can be manipulated by low-privileged users to achieve RCE. CPEs indicate both Splunk Enterprise and Cloud Platform. Could explain that Splunk uses this directory for app staging, and improper handling of file permissions allows malicious upload to trigger code execution, possibly through app validation or loading mechanisms. Educational. - risk_assessment: CVSS 7.1, vector AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H. So network attack, high complexity, low privileges required, user interaction required, scope unchanged, high impact on CIA. EPSS 0.13% (low probability of exploitation, 33rd percentile). Not in KEV. No POC evidence. SSVC: exploitation none, automatable no, technical impact total. So risk is moderate but not actively exploited. Complexity high and user interaction required reduce real-world risk. But total impact, so if exploited, serious. Compare: CVSS is high severity (7.1) but EPSS suggests low exploitation likelihood. Patches available. Real-world priority: apply patches as part of normal cadence, not emergency. Mention that despite low EPSS, the total impact makes it worth remediating. - affected_products: list products with version ranges. Splunk Enterprise: below 10.2.1, 10.0.5, 9.4.10, 9.3.11. Splunk Cloud Platform: below 10.4.2603.0, 10.3.2512.5, 10.2.2510.9, 10.1.2507.19, 10.0.2503.13, 9.3.2411.127. Reference to vendor advisory: https://advisory.splunk.com/advisories/SVD-2026-0403. No bullet points. - remediation: action: upgrade to fixed versions. Provide exact versions: Enterprise: 9.3.11, 9.4.10, 10.0.5, 10.2.1; Cloud: 9.3.2411.127, 10.0.2503.13, 10.1.2507.19, 10.2.2510.9, 10.3.2512.5, 10.4.2603.0. Workaround maybe not mentioned. Possibly restrict file upload permissions or restrict access to apptemp directory. But no specific workaround in description. I'll say: "Upgrade Splunk Enterprise to version 9.3.11, 9.4.10, 10.0.5, or 10.2.1, and Splunk Cloud Platform to 9.3.2411.127, 10.0.2503.13, 10.1.2507.19, 10.2.2510.9, 10.3.2512.5, or 10.4.2603.0. As a temporary mitigation if upgrading is not possible, restrict write access to the apptemp directory to trusted roles only, but this may impact app installation functionality. Consult advisory SVD-2026-0403." - exploit_scenario: realistic attack: low-privileged Splunk user (without admin/power) uploads a malicious file to the apptemp directory (which they can access) via a crafted request or through app upload functionality if allowed; the file is then processed by Splunk in a way that leads to code execution, potentially via loading a malicious app or configuration. Attack complexity high due to need to trigger processing. Example: "A low-privileged user authenticates to Splunk Web and uploads a specially crafted file to the apptemp directory via the app import feature. When Splunk processes the temporary file for app installation, the malicious payload executes, giving the attacker remote code execution on the Splunk server." - exploitation_conditions: specific prerequisites from description: "low-privileged user that does not hold the admin or power Splunk roles". So attacker must have any low-privileged role, not power/admin. Also, the user must be able to upload a file to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory. That directory might be writable by all authenticated users? The vulnerability is due to improper handling and insufficient isolation of temporary files. So condition: the Splunk instance must allow file uploads to apptemp by low-privileged users. It may be default. User interaction required (UI:R) could refer to the attacker needing to trick a user into processing? Actually UI:R in CVSS means the attacker must trick a user into taking some action. This might be that the low-privileged user must upload the file, but it's the attacker that is that user. In that case, it's not UI. Wait, CVSS says UI:R, which typically requires that the exploitation requires a user other than the attacker to take action. Could be that the attacker needs to convince a victim (another user) to upload the malicious file? The description says "a low-privileged user could potentially perform a Remote Code Execution by uploading a malicious file". That suggests the attacker is the low-privileged user themselves. So UI:R might be misinterpreted? Alternatively, the upload might be via some UI action that the attacker performs. But CVSS defines UI:R as "the vulnerable component requires user interaction to function. ... the user interaction is required from a user other than the attacker." So if the attacker themselves is the user performing the upload, then it's not UI:R but rather PR:L and no UI. The CVSS vector provided shows UI:R, but given descriptions, maybe the attacker must convince a user with low privileges to upload? Could be both: maybe the attacker can be a low-privileged user, but to trigger the RCE they need to interact with the apptemp directory in a way that involves some UI? Possibly the vulnerability is in the handling of uploaded files during app installation, which might be triggered by the user through UI. I think the vector might be AV:N/AC:H/PR:L/UI:N/..., but they put UI:R. I'll respect the given CVSS vector. So exploitation conditions: attacker must be authenticated as a low-privileged user (non-admin, non-power) and must be able to upload a file to apptemp, but also requires user interaction from another user? Perhaps the attacker uploads a file that is then executed when an admin installs or processes an app. That would be UI:R from the admin. So condition: "Exploitation requires an authenticated low-privileged user (without admin or power roles) to upload a malicious file to the apptemp directory, and a subsequent user action (e.g., by an administrator or automated process) that triggers processing of that file." But let's keep to the description. I'll state: "Requires an authenticated Splunk account with any low-privileged role (not admin or power). The attacker must be able to write files to the `$SPLUNK_HOME/var/run/splunk/apptemp` directory, which may be accessible by default. User interaction is required to trigger the RCE (CVSS UI:R), likely from another user such as an administrator performing an app management action." Also add that it's remote over network. So: "Exploitation requires authenticated access as a low-privileged user (non-admin, non-power) and the ability to upload files to the apptemp directory. No specific non-default configuration is required if the directory is writable; however, the high attack complexity and user interaction requirement imply that the attacker must either trick another user into processing the file or rely on specific workflow." - attack_chain: Based on kill chain: authenticated low-privileged user uploads malicious file to apptemp directory via Splunk Web or API → file is stored in apptemp with insufficient isolation → later, an administrator or cron job processes the file (e.g., during app installation or validation) → the malicious payload executes → attacker achieves remote code execution with Splunk service privileges. So chain: "Authenticate as low-privileged Splunk user → Upload malicious file to apptemp directory via app upload feature → Wait for file to be processed by Splunk (e.g., admin action or scheduled task) → Malicious code executes → Gain RCE on Splunk server." 5 steps. - confidence_notes: Vendor advisory exists (SVD-2026-0403) confirming affected versions and patches. EPSS score is low, no KEV. POC status unknown (not listed). The CVE description is from the advisory. SSVC indicates no exploitation, not automatable, total impact. So confidence: "Vendor-confirmed vulnerability with fixed versions published in Splunk advisory SVD-2026-0403. No evidence of public exploit or active exploitation. Affected version ranges and patch availability are confirmed. The exact mechanism of code execution and preconditions (UI:R) require further analysis." - prevalence: Splunk is a widely used enterprise SIEM and log management platform. It is common in large organizations. So prevalence likely "high". Many enterprise environments run Splunk. So "high". - prevalence_basis: "widely deployed enterprise SIEM and log management solution". - assessed_cvss_vector: I need to provide my own independent CVSS. Given the description, I might adjust. The provided CVSS is 7.1: AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H. Is that reasonable? The attack requires network, low privileges, but also user interaction. However, if the attacker is the low-privileged user and they upload a file and that immediately triggers RCE, then UI:N would be more appropriate. But the description doesn't say what triggers the RCE. Could be that the file is uploaded and then automatically processed by some Splunk internal mechanism without user interaction? The CWE-377 is Insecure Temporary File, but the vulnerability could be that the file is placed and then later processed by a service (like a cron job) that doesn't require user interaction. In that case, UI:N. However, the given vector has UI:R, which I'll respect because it's from Splunk themselves. So my assessed vector might differ. I'll reason: The attack requires the attacker to upload a file, but if the processing is automatic, then UI:N. But high complexity maybe due to file format or timing. I'll lean towards UI:N if the description doesn't mention tricking a user. But let's read: "could potentially perform a Remote Code Execution by uploading a malicious file to the $SPLUNK_HOME/var/run/splunk/apptemp directory due to improper handling". So the act of uploading is the vector. The handling is improper, so the mere upload might cause RCE. That suggests no additional user interaction. So I'd set UI:N. Also, the attack complexity: maybe needs specific file content? High? Might be high if
Arbitrary shell command execution in Splunk Enterprise and Cloud Platform allows authenticated users with the edit_cmd capability to inject commands through the unarchive_cmd parameter in the preview upload endpoint. Affected versions include Splunk Enterprise below 10.2.0, 10.0.4, 9.4.9, and 9.3.10, as well as corresponding Cloud Platform versions. An attacker with high-privilege roles could achieve remote code execution on vulnerable systems, though no patch is currently available.
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or power Splunk roles could cause a Remote Code Execution through an external lookup. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100, a low-privileged user who holds a role that has the ‘edit_user’ capability. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through the dashboard PDF generation component. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Actively exploited in the wild (cisa kev) and public exploit code available.
Partial API key exposure in Splunk On-Call (VictorOps) app versions below 1.0.43 allows any authenticated Splunk user - regardless of role - to read a partially masked VictorOps API key from the App Key Value Store (KV Store). The app fails to fully mask the API key prior to persisting it in a KV Store collection that is readable by low-privileged users who do not hold the 'admin' or 'power' Splunk roles, violating the principle of least-privilege for credential storage. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; the CVSS score of 4.3 aligns with the limited, partial credential exposure.
Unauthenticated ReDoS in Splunk Connect for Kafka below version 2.2.7 allows a network-accessible attacker to permanently block a Kafka Connect worker thread by submitting a pathological regular expression via the Kafka Connect REST API, which - when triggered by attacker-supplied or coincident matching event data during timestamp extraction - causes the regex engine to backtrack catastrophically without bound. The practical result is complete stoppage of event delivery for the targeted connector, constituting a targeted denial-of-service against Splunk data ingestion pipelines. No public exploit code or CISA KEV listing exists at time of analysis; the CVSS AC:H rating reflects the two-condition prerequisite, moderating the net risk score to 5.9 Medium despite the unauthenticated network vector.
Splunk Connect for Kafka below version 2.2.7 contains an uncontrolled resource consumption flaw in its HTTP Event Collector retry mechanism, enabling an unauthenticated network attacker who can also manipulate HEC endpoint responses to trigger an infinite retry loop that permanently halts Kafka-to-Splunk event delivery. The vulnerability arises because the connector applies an unbounded default retry count for failed HEC batches rather than a finite limit, causing the connector to stall indefinitely when fed persistent failure responses. No active exploitation has been confirmed - the vulnerability is not in CISA KEV - and no public exploit code has been identified at time of analysis.
Missing authorization in Splunk AI Toolkit below version 6.0.1 allows any authenticated low-privilege user to delete the experiment history belonging to another user via the REST API. The root cause is a sequencing flaw: the Toolkit executes the deletion operation before verifying whether the requesting user holds permission to delete the target experiment, violating the principle of check-before-act. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog; however, a patch is available in version 6.0.1.
Unauthenticated model content injection in Splunk AI Toolkit below 6.0.0 allows an authenticated attacker with model upload privileges to overwrite another user's in-progress model upload by racing concurrent requests to the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The root cause is the toolkit's failure to bind uploaded file content to the specific request that creates the corresponding model lookup entry, enabling a TOCTOU-style substitution. No public exploit code or CISA KEV listing has been identified; the vendor (Splunk) has released a patch in version 6.0.0.
Hard-coded and predictable credentials in Splunk AI Toolkit versions below 6.0.0 expose connected container services to unauthorized access by any low-privileged Splunk user. The toolkit generates or stores credentials for its container integrations using predictable or fixed default values, which are retrievable through the AI Toolkit Connections tab without requiring elevated Splunk roles. No public exploit has been identified at time of analysis, and no CISA KEV listing exists, but a vendor patch (6.0.0) is available per advisory SVD-2026-0808, reported by Cisco.
Unauthenticated exposure of the OpenAPI specification in Cisco Talos Intelligence for Enterprise Security Cloud (versions below 1.0.3) allows any network-accessible user to retrieve the add-on's full REST API documentation via Splunk Web static file paths. The disclosed specification reveals API endpoint structure and the authentication model, enabling reconnaissance that could facilitate targeted follow-on attacks. No active exploitation or public exploit code has been identified at time of analysis.
Cleartext exposure of Zoom meeting passwords in the Splunk SOAR interface affects all deployments running the Zoom app for Splunk SOAR below version 3.2.2. Any authenticated SOAR user holding a role with permission to run actions can invoke the create meeting, update meeting, or update user settings actions and observe meeting passwords and personal meeting ID (PMI) passwords in plaintext within the SOAR UI. No public exploit code has been identified at time of analysis, and this vulnerability is not listed in the CISA KEV catalog.
Cleartext credential exposure in Venafi app for Splunk SOAR versions below 2.1.4 allows any authenticated user with action-run permissions to read keystore and private-key passwords directly from the Splunk SOAR user interface. The root cause is that the app's `keystore_password` and `password` parameters in the 'get certificate' action are not flagged as password-type fields, bypassing the SOAR platform's native masking mechanism. No public exploit code identified at time of analysis, and there is no CISA KEV listing; however, the exposed credentials could enable downstream PKI compromise if observed by a malicious insider.
Cleartext exposure of archive passwords in Splunk Attack Analyzer Connector for Splunk SOAR (versions below 2.2.1) allows authenticated users with action-running permissions to view sensitive archive_password values unmasked in the SOAR user interface. The connector's detonate file and detonate url actions fail to mark the archive_password parameter as a password type, causing the SOAR framework to render it in plaintext during and after action execution. No active exploitation has been identified - the CVE carries no CISA KEV listing and no known public exploit code - but insider or compromised-account exposure is straightforward for any SOAR user with the relevant role.
Information disclosure in the RSA SecurID Authentication Manager app for Splunk SOAR (versions below 1.0.5) exposes RSA token serial numbers in cleartext to any authenticated user with action-run permissions. The app's 'enable token' and 'revoke token' actions fail to mark the token_serial parameter as a password field, causing it to render unmasked in the Splunk SOAR user interface. No public exploit has been identified at time of analysis, and exploitation is constrained by the requirement for an existing Splunk SOAR account with action-execution privileges.
Cleartext exposure of archive passwords in Splunk SOAR's Phantom app (versions below 3.8.5) allows authenticated users with action-running permissions to read sensitive credentials directly from the platform's user interface. The deflate item action fails to mark its password parameter as a sensitive field, causing the archive password to be rendered in plaintext in the SOAR UI to any user who invokes the action. Splunk has released a patch in version 3.8.5 per advisory SVD-2026-0806; no public exploit code or CISA KEV listing has been identified at time of analysis.
Cleartext exposure of temporary Active Directory passwords in the MS Graph for Active Directory app for Splunk SOAR (versions below 1.5.2) allows authenticated users with action-run permissions to capture credentials generated during password reset operations, as the temp_password parameter is rendered in plaintext in the SOAR interface rather than being masked. The flaw stems from the app failing to declare the affected parameter as a password type, causing the Splunk SOAR UI to treat it as generic text output. No active exploitation has been confirmed and no public POC is reported; risk is bounded by the requirement for an authenticated internal SOAR account with specific action-run role permissions.
Cleartext exposure of document passwords in the CrowdStrike OAuth API app for Splunk SOAR (versions below 5.1.3) allows any authenticated user with action-running permissions to read sensitive document_password values directly from the Splunk SOAR user interface. The root cause is the app's failure to mark the document_password parameter as a password type in both the detonate file and detonate url actions, meaning the platform's built-in masking mechanism is never invoked. Vendor patch version 5.1.3 has been released and confirmed via Splunk advisory SVD-2026-0806; no public exploit code or active exploitation has been identified at time of analysis.
Information disclosure in the Cisco Webex App for Splunk SOAR (versions below 2.2.1) exposes Webex meeting passwords in cleartext within the SOAR platform interface. Authenticated users holding roles with action-execution permissions who invoke the 'schedule meeting' action can read the plaintext meeting password directly from the UI, because the app's action manifest fails to designate the password parameter as a masked field. No active exploitation has been identified (not in CISA KEV) and no public exploit code is known; real-world impact is bounded by the requirement for existing SOAR action permissions.
Cleartext exposure of a sensitive sample password in the Cisco Secure Malware Analytics App for Splunk SOAR (versions below 2.4.5) allows authenticated users with action-run permissions to read the sample_password parameter value directly from the Splunk SOAR user interface. The root cause is the app's failure to mark the sample_password field as a password type in the detonate file action, meaning the platform never applies its standard masking behavior to that parameter. No public exploit code or active exploitation has been identified; vendor patch is available at version 2.4.5.
Cleartext exposure of temporary passwords in the Azure AD Graph app for Splunk SOAR (versions below 2.5.3) allows authenticated action-runners to read Azure AD reset credentials directly from the SOAR interface. The app's reset password action fails to classify the temp_password parameter as a sensitive field, so Splunk SOAR renders it unmasked in the UI rather than applying its standard password-masking behavior. Vendor patch 2.5.3 is available per Splunk advisory SVD-2026-0806; no public exploit code and no CISA KEV listing identified at time of analysis.
Credential exposure in the AWS IAM App for Splunk SOAR (all versions below 2.1.9) enables any authenticated user holding a role with action-execution permission to view AWS credentials in cleartext directly within the Splunk SOAR user interface. The root cause is the app's failure to designate the credentials action parameter as a password type field (CWE-312), causing the SOAR platform to render it unmasked rather than redacted. No active exploitation (CISA KEV) or public exploit code has been identified; however, because the exposed material consists of AWS access credentials rather than generic application data, the downstream business risk - potential cloud account compromise - substantially exceeds what the CVSS 4.3 Medium score conveys.
Credential exposure in the AD LDAP app for Splunk SOAR (versions below 2.3.8) allows any authenticated user holding an action-execution role to trigger a full connector process environment dump to a persistent plaintext debug log file, disclosing sensitive credentials such as LDAP bind secrets or service account tokens. The CVSS scope-changed vector (S:C) reflects that the exposed credentials extend impact beyond the SOAR platform itself to the underlying Active Directory environment. No public exploit code exists and this vulnerability is not listed in CISA KEV at time of analysis; however, patch version 2.3.8 is available and should be applied promptly given the potential for AD credential theft.
Sensitive Active Directory response data exposure in the AD LDAP App for Splunk SOAR (versions below 2.3.8) allows authenticated users holding action-execution permissions to cause AD directory data to be written to a persistent debug log file. The flaw is rooted in CWE-532 (insertion of sensitive information into log files) and is reachable over the network by any low-privileged SOAR user with the appropriate role. No public exploit code or active exploitation has been identified; Splunk has released a patch at version 2.3.8.
LDAP injection in the AD LDAP app for Splunk SOAR (versions below 2.3.8) allows authenticated low-privileged users to manipulate Active Directory queries, exposing account enumeration, sensitive attribute disclosure, and unintended modification of AD objects. Exploitation requires only a role with 'run actions' permission within Splunk SOAR - no elevated SOAR admin rights needed. Splunk has released a patch (version 2.3.8); no public exploit code or CISA KEV listing has been identified at time of analysis.
The Nmap Scanner connector for Splunk SOAR (versions prior to 3.0.15) permits privileged users to bypass Safe Mode playbook restrictions by exploiting a manifest miscategorization that marks the scan network action as read-only despite its accepting NSE script parameters capable of write operations and command execution on target systems. Users holding roles that allow editing, creating, or running playbooks can leverage this gap to run arbitrary Nmap Scripting Engine scripts against networked targets through SOAR automation - a meaningful privilege escalation given SOAR platforms typically have broad network reach. No public exploit has been identified at time of analysis, and a vendor patch is available via Splunk advisory SVD-2026-0806.
FireAMP connector versions below 2.1.15 for Splunk SOAR allow authenticated playbook editors to bypass Safe Mode restrictions by invoking the add listitem action, which the connector manifest incorrectly classifies as read-only despite it performing write operations on file lists. Exploitation requires a high-privilege role (playbook edit/create/run), limiting the attack surface to trusted internal SOAR users. No public exploit code exists and this vulnerability has not been identified in CISA KEV, consistent with its low CVSS score of 2.7.
Splunk SOAR versions below 8.6.0 expose tenant names and identifiers to authenticated users whose roles restrict them to a subset of tenants, due to a REST API authorization enforcement gap. In multi-tenant deployments, a low-privileged user can enumerate out-of-scope tenant metadata - names and identifiers - without triggering any access control check. No active exploitation or public exploit code has been identified; the CVSS score of 4.3 (Medium) reflects limited confidentiality impact with no integrity or availability consequence.
Path traversal in Splunk SOAR below 8.6.0 enables users holding the OnPrem Broker role to write files to arbitrary locations outside the designated Automation Broker log directory. The flaw stems from the log upload endpoint accepting crafted filenames without adequate sanitization, allowing directory traversal sequences to escape the intended write boundary. No public exploit has been identified and no active exploitation is confirmed; the CVSS score of 2.7 (Low) accurately reflects the high privilege prerequisite and the limited, integrity-only impact.
Splunk SOAR versions below 8.6.0 expose a missing authorization flaw in the Playbook History feature that allows authenticated users holding the `playbooks:view` permission to read metadata about playbook repositories they are not explicitly authorized to access. The Playbook History endpoint omits repository-level permission checks before returning revision metadata, enabling unauthorized information disclosure within role-segregated SOAR deployments. No active exploitation has been confirmed - there is no CISA KEV listing and no public exploit code has been identified - and the CVSS base score of 2.7 reflects the high-privilege prerequisite and narrow confidentiality-only impact scope.
Stored XSS in Splunk SOAR below 8.6.0 enables an authenticated 'Incident Commander' role user to inject JavaScript into a note, which executes in the browser of any user who subsequently opens it. The flaw stems from unsanitized HTML rendering triggered by a note format change, meaning content stored safely in one format becomes executable in another. No public exploit code exists and the vulnerability is absent from CISA KEV; however, successful exploitation could compromise victim session integrity within the SOAR platform.
Session token disclosure in Splunk SOAR versions below 8.6.0 enables any authenticated account holder to recover session tokens belonging to other users by manipulating REST API filters on the playbook run endpoint. Because Splunk SOAR fails to block filter predicates from matching against values that are otherwise suppressed in API responses, an attacker with a low-privilege account can systematically extract credentials granting full access to any targeted user's data within the platform. Splunk has released version 8.6.0 as a fix; no public exploit has been identified at time of analysis, but the low attack complexity elevates urgency for organizations where multiple users share a SOAR instance.