IBM watsonx.data versions 2.4.0 through 2.4.0 patch 8 contain an improper access control vulnerability that could allow a remote attacker to obtain sensitive information. The vulnerability is identified as CVE-2026-14885 and has a medium severity rating with a CVSS score of 4.8. No public exploits or known active exploitation have been reported. No patch or remediation details are currently provided.
Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5 contain a vulnerability where users without 'admin' or 'power' roles can configure metric alerts via the REST API that execute searches with elevated privileges. This occurs due to improper enforcement of role-based authorization during metric alert configuration, allowing unauthorized users to access or modify data and disrupt the Splunk instance.
Splunk Enterprise versions prior to 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where users with the "power" role can inject attacker-controlled Search Processing Language (SPL) into shared data model calculations. When other users run searches against these shared data models, the injected SPL executes with their permissions, potentially exposing sensitive credentials. This occurs because Splunk does not properly neutralize data model calculation fields before including them in generated searches.
A vulnerability in Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16 allows non-admin and non-power users to execute arbitrary Search Processing Language (SPL) commands via scheduled metric alert searches. This flaw arises from insufficient validation of metric alert filter inputs and requires at least one non-internal metric index on the instance.
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated attacker can trick an active Splunk Web user into running arbitrary SPL searches via a crafted link. This can potentially expose stored credentials and indexed data. Exploitation requires phishing the user to open the malicious link. The vulnerability arises from improper neutralization of user-controlled data when generating SPL searches for field reports.
A vulnerability in Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 allows a user with the "power" role to store attacker-controlled Search Processing Language (SPL) in a shared data model. This occurs because the Data Model Editor does not properly neutralize data model field names when building a preview search. Exploitation requires phishing the affected user to initiate a request in their browser, limiting the attacker's ability to exploit at will.
Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated user can enumerate valid usernames via the REST API or Splunk Web. This is due to differing login failure responses for locked accounts versus nonexistent usernames. Additionally, repeated login attempts can lock out existing user accounts.
Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16 contain a vulnerability where non-admin and non-power users can access indexed events that should be hidden by their role's srchFilter setting via the search jobs REST API. Additionally, these users can bypass SPL safeguards for risky commands within indexes they can search. This occurs because required field values are not properly escaped in internally generated searches.
Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where users lacking the list_indexer_cluster or edit_indexer_cluster capabilities can download the cluster manager configuration bundle via the REST API. This bundle includes configuration and app files staged for indexer distribution. The flaw exists because the REST API does not enforce capability checks before providing access to this bundle.
A vulnerability in Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16 allows non-admin and non-power users to execute arbitrary Search Processing Language (SPL) searches with elevated privileges via data model acceleration. This occurs because Splunk Enterprise does not properly sanitize user-supplied data model acceleration values before incorporating them into summarization searches.
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where an unauthenticated user can exploit an empty clustering shared secret to access and modify clustering configuration via the REST API on standalone instances. This flaw arises because the software accepts an empty shared secret as valid when clustering is disabled, potentially exposing sensitive configuration and disrupting cluster operations.
Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where users without 'admin' or 'power' roles can view email notification credentials in saved searches shared with them. This occurs because the Saved Searches REST API returns these credentials in clear text when email notifications use authentication. The vulnerability has a medium severity with a CVSS score of 4.3.
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 on Ubuntu and AlmaLinux contain a session management vulnerability. An unauthenticated attacker who obtains a valid Splunk Web session cookie before the user logs out can continue to use that cookie after logout to access the user's data and perform actions. This occurs because the logout process does not invalidate the session token. The vulnerability requires the attacker to acquire the session cookie prior to logout.
ServiceNow addressed an indirect prompt injection vulnerability in the Email Response AI Agent of Now Assist for CSM. The issue was remediated centrally without requiring platform upgrades or hotfixes. There are no known malicious exploits targeting this vulnerability at this time.
Splunk Enterprise for Windows versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 contain a vulnerability where users with the edit_user capability can create multiple accounts that share the same user directory. This occurs due to improper validation of usernames and Windows filesystem behavior that removes trailing periods from directory names, causing distinct usernames to map to the same directory. This can lead to exposure or modification of user-specific configurations and disruption of features relying on separate user directories.
Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability allowing unauthenticated users to execute arbitrary SPL searches via RapidDiag task collection. This occurs because the product accepts an empty shared secret during authentication of RapidDiag requests, enabling unauthorized access to data and configuration accessible to authenticated users.
Splunk AI Assistant versions below 2.0.0 contain a vulnerability where users without admin or power roles can submit client-controlled feature settings via the REST API. This allows modification of limited response metadata beyond the intended server-side configuration boundaries.
Splunk AI Assistant versions below 2.0.0 contain a vulnerability where users without admin or power roles can access data from other tenants and perform actions attributed to those tenants via the REST API. This occurs because the software accepts a client-controlled tenant identifier for authorization context selection.
A resource release issue exists in netty-incubator-codec-ohttp versions from 0.0.20.Final up to but not including 0.0.27.Final. The OHttpClientCodec and OHttpServerCodec components retain the outer cumulation buffer after an OHTTP exchange completes, causing memory to be held unnecessarily during long-lived idle keep-alive connections. This can lead to increased memory usage and availability pressure. The issue is fixed in version 0.0.27.Final.
Splunk AI Assistant versions below 2.0.0 contain a vulnerability where users without 'admin' or 'power' roles can enable the AI chat training-data consent setting via the REST API due to missing authorization checks on the configuration endpoint.