CVE-2023-46214

CRITICALNVD 8.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 89% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized
9.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 89%
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 89%CVSS: 8.8Exploit: MetasploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Splunk) lists Splunk Enterprise versions 9.0 up to but not including 9.0.7 and 9.1 up to but not including 9.1.2; Splunk Cloud versions before 9.1.2308 as affected. No release containing a fix is confirmed on record.

In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply. This means that an attacker can upload malicious XSLT which can result in remote code execution on the Splunk Enterprise instance.

CVSS v3
8.8
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation89% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
89%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.8 HIGH): a likelihood of exploitation, not impact.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
89% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 16, 2023

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 31, 2026
No fix on record yet.
Web page

https://research.splunk.com/removed/a053e6a6-2146-483a-9798-2d43652f3299/

https://research.splunk.com/application/a053e6a6-2146-483a-9798-2d43652f3299/
Web page

Detection: Splunk RCE via User XSLT | Splunk Security Content

https://research.splunk.com/application/6cb7e011-55fb-48e3-a98d-164fa854e37e/
Web page

SVD-2023-1104 | Splunk Vulnerability Disclosure

https://advisory.splunk.com/advisories/SVD-2023-1104

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 80 of 88 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 20 repeat rows among the latest 100 are merged into the row they repeat. The 8 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:13 UTCEG score recompute
  2. 2026-10-23 16:13 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  3. 2026-10-22 14:17 UTCEG score recompute
  4. 2026-10-22 14:17 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  5. 2026-10-21 16:29 UTCEPSS rescoreEPSS 89% · 99th percentile
  6. 2026-10-21 12:22 UTCEG score recompute
  7. 2026-10-21 12:22 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  8. 2026-10-20 10:28 UTCEG score recompute
  9. 2026-10-20 10:27 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  10. 2026-10-19 08:33 UTCEG score recompute
  11. 2026-10-19 08:33 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  12. 2026-10-18 06:38 UTCEG score recompute
  13. 2026-10-18 06:38 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  14. 2026-10-17 04:45 UTCEG score recompute
  15. 2026-10-17 04:45 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  16. 2026-10-16 02:50 UTCEG score recompute
  17. 2026-10-16 02:49 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  18. 2026-10-15 16:29 UTCEPSS rescoreEPSS 89% · 99th percentile
  19. 2026-10-14 22:52 UTCEG score recompute
  20. 2026-10-14 22:52 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  21. 2026-10-14 16:30 UTCEPSS rescoreEPSS 89% · 99th percentile
  22. 2026-10-13 18:32 UTCEG score recompute
  23. 2026-10-13 18:31 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
  24. 2026-10-12 16:36 UTCEG score recompute
  25. 2026-10-12 16:36 UTCGHSA enrichmentGHSA-mwwq-v92j-38xr · GitHub severity HIGH · GitHub CVSS 8.0
Show 55 more
  1. 2026-10-11 21:43 UTCEG score recompute
  2. 2026-10-09 20:05 UTCEPSS rescoreEPSS 89% · 99th percentile
  3. 2026-10-06 15:15 UTCEPSS rescoreEPSS 89% · 99th percentile
  4. 2026-09-30 16:32 UTCEG score recompute
  5. 2026-09-30 15:01 UTCEPSS rescoreEPSS 89% · 99th percentile
  6. 2026-09-28 13:49 UTCEPSS rescoreEPSS 89% · 99th percentile
  7. 2026-09-24 14:01 UTCEPSS rescoreEPSS 89% · 99th percentile
  8. 2026-09-22 14:46 UTCEPSS rescoreEPSS 89% · 99th percentile
  9. 2026-09-21 20:31 UTCEPSS rescoreEPSS 89% · 99th percentile
  10. 2026-09-20 20:14 UTCEPSS rescoreEPSS 89% · 99th percentile
  11. 2026-09-17 19:25 UTCEPSS rescoreEPSS 89% · 99th percentile
  12. 2026-09-16 05:11 UTCEPSS rescoreEPSS 89% · 99th percentile
  13. 2026-09-07 15:59 UTCEPSS rescoreEPSS 89% · 99th percentile
  14. 2026-09-06 13:45 UTCEPSS rescoreEPSS 89% · 99th percentile
  15. 2026-09-05 15:26 UTCEPSS rescoreEPSS 89% · 99th percentile
  16. 2026-09-04 13:58 UTCEPSS rescoreEPSS 89% · 99th percentile
  17. 2026-08-30 19:15 UTCEPSS rescoreEPSS 89% · 99th percentile
  18. 2026-08-30 01:20 UTCEPSS rescoreEPSS 89% · 99th percentile
  19. 2026-08-28 21:39 UTCEPSS rescoreEPSS 89% · 99th percentile
  20. 2026-08-27 14:23 UTCEPSS rescoreEPSS 89% · 99th percentile
  21. 2026-08-24 14:14 UTCEPSS rescoreEPSS 89% · 99th percentile
  22. 2026-08-21 23:47 UTCEPSS rescoreEPSS 89% · 99th percentile
  23. 2026-08-19 17:02 UTCEPSS rescoreEPSS 89% · 99th percentile
  24. 2026-08-18 13:46 UTCEPSS rescoreEPSS 89% · 99th percentile
  25. 2026-08-16 02:12 UTCEPSS rescoreEPSS 89% · 99th percentile
  26. 2026-08-12 13:49 UTCEPSS rescoreEPSS 89% · 99th percentile
  27. 2026-08-01 04:14 UTCEPSS rescoreEPSS 89% · 99th percentile
  28. 2026-07-28 15:34 UTCEPSS rescoreEPSS 89% · 99th percentile
  29. 2026-07-24 14:16 UTCEPSS rescoreEPSS 89% · 99th percentile
  30. 2026-07-23 02:27 UTCEG score recompute
  31. 2026-07-22 23:14 UTCEG score recompute
  32. 2026-07-22 14:06 UTCEPSS rescoreEPSS 89% · 99th percentile
  33. 2026-07-19 02:27 UTCEPSS rescoreEPSS 89% · 99th percentile
  34. 2026-07-16 17:01 UTCEPSS rescoreEPSS 89% · 99th percentile
  35. 2026-07-15 16:56 UTCEPSS rescoreEPSS 89% · 99th percentile
  36. 2026-07-12 05:45 UTCEPSS rescoreEPSS 89% · 99th percentile
  37. 2026-07-06 16:26 UTCEPSS rescoreEPSS 89% · 99th percentile
  38. 2026-07-06 02:22 UTCEPSS rescoreEPSS 89% · 99th percentile
  39. 2026-07-05 02:29 UTCEPSS rescoreEPSS 89% · 99th percentile
  40. 2026-06-30 23:21 UTCEPSS rescoreEPSS 89% · 99th percentile
  41. 2026-06-25 13:48 UTCEPSS rescoreEPSS 89% · 99th percentile
  42. 2026-06-24 14:04 UTCEPSS rescoreEPSS 89% · 99th percentile
  43. 2026-06-24 06:30 UTCNVD updateCVSS v3 → 8.8
  44. 2026-06-23 21:31 UTCEPSS rescoreEPSS 89% · 99th percentile
  45. 2026-06-15 17:47 UTCEPSS rescoreEPSS 89% · 99th percentile
  46. 2026-06-14 23:16 UTCEPSS rescoreEPSS 88% · 99th percentile
  47. 2026-06-12 23:10 UTCEPSS rescoreEPSS 88% · 99th percentile
  48. 2026-06-10 22:17 UTCEPSS rescoreEPSS 88% · 99th percentile
  49. 2026-06-10 13:21 UTCEPSS rescoreEPSS 88% · 99th percentile
  50. 2026-06-08 14:16 UTCEPSS rescoreEPSS 88% · 99th percentile
  51. 2026-06-07 15:23 UTCEPSS rescoreEPSS 88% · 99th percentile
  52. 2026-06-06 13:46 UTCEPSS rescoreEPSS 88% · 99th percentile
  53. 2026-06-05 22:46 UTCEPSS rescoreEPSS 88% · 99th percentile
  54. 2026-06-04 13:11 UTCEPSS rescoreEPSS 88% · 99th percentile
  55. 2026-05-31 22:30 UTCEPSS rescoreEPSS 88% · 99th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitexploit/unix/http/splunk_xslt_authenticated_rce✓ verified
    Published Dec 11, 2023

    Splunk Authenticated XSLT Upload RCE

    Open source ↗

Frequently asked(5)

What is CVE-2023-46214?
CVE-2023-46214 is a critical-severity vulnerability; its CVE record was published on November 16, 2023. In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet language transformations (XSLT) that users supply. This means that an attacker can upload malicious XSLT which can result in remote code execution on the Splunk Enterprise instance.
When was CVE-2023-46214 made public?
CVE-2023-46214 was made public on November 16, 2023: that is the date its CVE record's CNA, Splunk, gives for when the vulnerability was made public. The CVE record itself was published on November 16, 2023. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2023-46214 actively exploited?
CVE-2023-46214 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-46214?
CVE-2023-46214 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-46214?
No fix for CVE-2023-46214 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Splunk) lists Splunk Enterprise versions 9.0 up to but not including 9.0.7 and 9.1 up to but not including 9.1.2; Splunk Cloud versions before 9.1.2308 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-46214

Explore →

Is Your Infrastructure Affected by CVE-2023-46214?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.