Skip to main content
Menu
CVEs

Splunk Enterprise credential disclosure in saved searches REST API

CVE-2026-76532Published November 19, 2026, updated

4.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17
Who is exposed
Not reported

Summary

In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold the "admin" or "power" Splunk roles could view credentials configured for email notifications in a saved search shared with that user. The vulnerability is possible when email notifications use authentication credentials because the Saved Searches Representational State Transfer (REST) API returns those credentials in clear text. For more information see Search endpoint descriptions (help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.6/search-endpoints/search-endpoint-descriptions), Manage knowledge object permissions (help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.6/get-started-with-knowledge-objects/manage-knowledge-object-permissions), and Email notification action (help.splunk.com/en/splunk-enterprise/alert-and-respond/alerting-manual/10.6/configure-alert-actions/email-notification-action) in the Splunk documentation.

What to do

Upgrade to a fixed version: 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-76532 (Sensitive Information Disclosure through the Saved Searches REST API 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-76532 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise: from 10.6, fixed in 10.6.1; 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.17
Fixed versions: 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-76532 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76532 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
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-76532
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-76532"}.

Affected versions

cve.now Index

7Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.3/10CVSS 4.3
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1103
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-76532
RecordNVD · CVE-2026-76532

Questions about CVE-2026-76532

Is CVE-2026-76532 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: cve.now feed data

Which versions are affected by CVE-2026-76532?

Splunk Enterprise: from 10.6 before 10.6.1; 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.17.

Source: cve.now feed data

How do I fix CVE-2026-76532?

Upgrade to a fixed version: 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.