Cyber Resilience

CVE-2026-20239

High

Published: 20 May 2026

Published
20 May 2026
Modified
21 May 2026
KEV Added
Patch
CVSS Score v3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0049 37.9th percentile
Risk Priority 15 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2026-20239 is a high-severity Insertion of Sensitive Information into Log File (CWE-532) vulnerability in Splunk Splunk Cloud Platform. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 37.9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability details

In Splunk Enterprise versions below 10.2.2 and 10.0.5, and Splunk Cloud Platform versions below 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 10.0.2503.13, a user with a role that has access to the `_internal` index could view session cookies and response bodies that contain…

more

sensitive data.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-20163Same product: Splunk Splunk
CVE-2026-20204Same product: Splunk Splunk
CVE-2025-20229Same product: Splunk Splunk
CVE-2025-20231Same product: Splunk Splunk
CVE-2026-28987Shared CWE-532
CVE-2025-24984Shared CWE-532
CVE-2025-0976Shared CWE-532
CVE-2026-32982Shared CWE-532
CVE-2026-34487Shared CWE-532
CVE-2024-48852Shared CWE-532

Affected Assets

splunk
splunk
10.0.0 — 10.0.5 · 10.2.0 — 10.2.2
splunk
splunk cloud platform
10.0.2503 — 10.0.2503.13 · 10.1.2507 — 10.1.2507.21 · 10.2.2510 — 10.2.2510.11

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-532

Procedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.

addresses: CWE-532

Identifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.

addresses: CWE-532

Cross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.

addresses: CWE-532

Identifying logging as a data action allows prevention of sensitive information being inserted into log files.

addresses: CWE-532

The process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.

addresses: CWE-532

Specific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.

addresses: CWE-532

PIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.

addresses: CWE-532

Limits insertion of sensitive operational details into logs by treating such data as key information requiring protection.

References