In Splunk Enterprise versions below 9.1.0.2, 9.0.5.1, and 8.2.11.2, an attacker can inject American National Standards Institute (ANSI) escape codes into Splunk log files that, when a vulnerable terminal application reads them, can potentially, at worst, result in possible code execution in the vulnerable application. This attack requires a user to use a terminal application that supports the translation of ANSI escape codes to read the malicious log file locally in the vulnerable terminal, and to perform additional user interaction to exploit. Universal Forwarder versions 9.1.0.1, 9.0.5, 8.2.11, and lower can be vulnerable in situations where they have management services active and accessible over the network. Universal Forwarder versions 9.0.x and 9.1.x bind management services to the local machine and are not vulnerable in this specific configuration. See SVD-2022-0605 for more information. Universal Forwarder versions 9.1 use Unix Domain Sockets (UDS) for communication, which further reduces the potential attack surface. The vulnerability does not directly affect Splunk Enterprise or Universal Forwarder. The indirect impact on Splunk Enterprise and Universal Forwarder can vary significantly depending on the permissions in the vulnerable terminal application and where and how the user reads the malicious log file. For example, users can copy the malicious file from the Splunk Enterprise instance and read it on their local machine.
CVE-2023-32712
This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 8.6
- EG Score
- 8.6HIGHmedium confidence
- EG Risk
- 39EG Risk 39/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.3%
- EPSS %ILE
- 25th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
June 1, 2023
Last Modified
November 21, 2024
Advisory Details (2)
Auto-updated Sep 1, 2026https://research.splunk.com/removed/de3908dc-1298-446d-84b9-fa81d37e959b/
https://research.splunk.com/application/de3908dc-1298-446d-84b9-fa81d37e959bSVD-2023-0606 | Splunk Vulnerability Disclosure
https://advisory.splunk.com/advisories/SVD-2023-0606Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 23× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 180 total refreshes for this CVE.
- 2026-10-09 20:05 UTCEPSS rescore
- 2026-10-08 17:06 UTCEPSS rescore
- 2026-10-07 23:46 UTCEPSS rescore
- 2026-10-06 15:15 UTCEPSS rescore
- 2026-10-05 17:41 UTCEPSS rescore
- 2026-10-04 23:20 UTCEPSS rescore
- 2026-10-03 14:23 UTCEPSS rescore
- 2026-09-30 16:23 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescore
- 2026-09-29 15:16 UTCEPSS rescore
- 2026-09-28 13:49 UTCEPSS rescore
- 2026-09-27 13:42 UTCEPSS rescore
- 2026-09-26 15:55 UTCEPSS rescore
- 2026-09-26 00:22 UTCEPSS rescore
- 2026-09-24 14:01 UTCEPSS rescore
- 2026-09-24 14:01 UTCEPSS rescore
- 2026-09-23 13:45 UTCEPSS rescore
- 2026-09-22 14:45 UTCEPSS rescore
- 2026-09-20 20:14 UTCEPSS rescore
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-13 16:44 UTCEPSS rescore
- 2026-09-12 14:58 UTCEPSS rescore
- 2026-09-11 09:34 UTCEPSS rescore
- 2026-09-08 21:57 UTCEPSS rescore
- 2026-09-07 15:59 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:26 UTCEPSS rescore
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-08-30 19:15 UTCEPSS rescore
- 2026-08-30 01:20 UTCEPSS rescore
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-27 14:23 UTCEPSS rescore
- 2026-08-26 14:43 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-24 14:14 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:47 UTCEPSS rescore
- 2026-08-20 22:53 UTCEPSS rescore
- 2026-08-19 17:02 UTCEPSS rescore
- 2026-08-18 13:46 UTCEPSS rescore
- 2026-08-17 13:45 UTCEPSS rescore
- 2026-08-16 14:54 UTCEPSS rescore
- 2026-08-16 02:12 UTCEPSS rescore
- 2026-08-15 01:28 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-11 13:39 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:34 UTCEPSS rescore
- 2026-08-07 16:24 UTCEPSS rescore
- 2026-08-06 13:44 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-04 10:35 UTCEPSS rescore
- 2026-08-03 10:34 UTCEPSS rescore
- 2026-08-02 02:25 UTCEPSS rescore
- 2026-08-01 04:13 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 16:26 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:34 UTCEPSS rescore
- 2026-07-27 14:10 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:16 UTCEPSS rescore
- 2026-07-24 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:23 UTCEG score recompute
- 2026-07-22 23:10 UTCEG score recompute▲ 5.20
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
- 2026-07-08 15:13 UTCEPSS rescore
- 2026-07-07 13:44 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2023-32712?
When was CVE-2023-32712 disclosed?
Is CVE-2023-32712 actively exploited?
What is the CVSS score of CVE-2023-32712?
How do I remediate CVE-2023-32712?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-32712
Is Your Infrastructure Affected by CVE-2023-32712?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.