Splunk Enterprise vulnerabilities: known CVEs & security history
Splunk · SIEM / observability · 112 tracked CVEs · 1 actively exploited · updated November 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Splunk Enterprise release lines — 112 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Splunk Enterprise's current status and the safe version to run.
Known Splunk Enterprise CVEs
Actively-exploited and most-severe first. Showing the top 80 of 112. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-20253⚡ exploited | critical | 9.8 | 88% | 2026 |
| CVE-2026-76285 | critical | 9.8 | 0% | 2026 |
| CVE-2026-76284 | critical | 9.8 | 0% | 2026 |
| CVE-2026-76268 | critical | 9.8 | 0% | 2026 |
| CVE-2026-76312 | critical | 9.4 | 0% | 2026 |
| CVE-2026-76311 | critical | 9.4 | 0% | 2026 |
| CVE-2026-76310 | critical | 9.4 | 0% | 2026 |
| CVE-2026-76298 | high | 8.8 | 0% | 2026 |
| CVE-2026-76291 | high | 8.8 | 0% | 2026 |
| CVE-2026-76282 | high | 8.8 | 0% | 2026 |
| CVE-2026-76352 | high | 8.8 | 0% | 2026 |
| CVE-2026-76351 | high | 8.8 | 0% | 2026 |
| CVE-2026-76350 | high | 8.8 | 0% | 2026 |
| CVE-2026-76335 | high | 8.8 | 0% | 2026 |
| CVE-2026-76319 | high | 8.8 | 0% | 2026 |
| CVE-2026-76317 | high | 8.8 | 0% | 2026 |
| CVE-2026-76316 | high | 8.8 | 0% | 2026 |
| CVE-2026-76315 | high | 8.8 | 0% | 2026 |
| CVE-2026-76314 | high | 8.8 | 1% | 2026 |
| CVE-2026-76313 | high | 8.8 | 0% | 2026 |
| CVE-2026-76259 | high | 8.8 | 0% | 2026 |
| CVE-2026-76253 | high | 8.8 | 0% | 2026 |
| CVE-2026-20296 | high | 8.3 | 0% | 2026 |
| CVE-2026-76354 | high | 8.1 | 0% | 2026 |
| CVE-2026-76338 | high | 8.1 | 0% | 2026 |
| CVE-2026-76331 | high | 8.1 | 0% | 2026 |
| CVE-2026-76266 | high | 7.7 | 0% | 2026 |
| CVE-2026-76344 | high | 7.7 | 0% | 2026 |
| CVE-2026-76283 | high | 7.6 | 0% | 2026 |
| CVE-2026-76290 | high | 7.5 | 0% | 2026 |
| CVE-2026-76288 | high | 7.5 | 0% | 2026 |
| CVE-2026-76355 | high | 7.5 | 0% | 2026 |
| CVE-2026-76262 | high | 7.5 | 0% | 2026 |
| CVE-2026-76254 | high | 7.5 | 0% | 2026 |
| CVE-2026-20239 | high | 7.5 | 0% | 2026 |
| CVE-2025-20371 | high | 7.5 | 0% | 2025 |
| CVE-2026-76325 | high | 7.3 | 0% | 2026 |
| CVE-2026-76321 | high | 7.3 | 0% | 2026 |
| CVE-2026-76293 | high | 7.2 | 0% | 2026 |
| CVE-2026-20297 | high | 7.2 | 0% | 2026 |
| CVE-2026-76336 | high | 7.1 | 0% | 2026 |
| CVE-2026-76333 | high | 7.1 | 0% | 2026 |
| CVE-2026-76332 | high | 7.1 | 0% | 2026 |
| CVE-2026-76330 | high | 7.1 | 0% | 2026 |
| CVE-2026-76251 | high | 7.1 | 0% | 2026 |
| CVE-2026-20204 | high | 7.1 | 3% | 2026 |
| CVE-2026-76252 | medium | 6.8 | 0% | 2026 |
| CVE-2026-76328 | medium | 6.7 | 0% | 2026 |
| CVE-2026-76322 | medium | 6.7 | 0% | 2026 |
| CVE-2026-20202 | medium | 6.6 | 0% | 2026 |
| CVE-2026-76292 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76289 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76274 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76271 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76270 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76269 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76265 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76343 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76260 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76258 | medium | 6.5 | 0% | 2026 |
| CVE-2026-76257 | medium | 6.5 | 0% | 2026 |
| CVE-2026-20240 | medium | 6.5 | 0% | 2026 |
| CVE-2025-20366 | medium | 6.5 | 0% | 2025 |
| CVE-2026-76349 | medium | 6.4 | 0% | 2026 |
| CVE-2026-76334 | medium | 6.4 | 0% | 2026 |
| CVE-2026-76329 | medium | 6.4 | 0% | 2026 |
| CVE-2026-76327 | medium | 6.4 | 0% | 2026 |
| CVE-2026-76323 | medium | 6.4 | 0% | 2026 |
| CVE-2026-76255 | medium | 6.4 | 0% | 2026 |
| CVE-2026-76280 | medium | 6.3 | 0% | 2026 |
| CVE-2026-76345 | medium | 6 | 0% | 2026 |
| CVE-2026-76320 | medium | 5.9 | 0% | 2026 |
| CVE-2026-76326 | medium | 5.7 | 0% | 2026 |
| CVE-2026-76324 | medium | 5.7 | 0% | 2026 |
| CVE-2026-76318 | medium | 5.7 | 0% | 2026 |
| CVE-2025-20368 | medium | 5.7 | 0% | 2025 |
| CVE-2025-20367 | medium | 5.7 | 0% | 2025 |
| CVE-2026-76287 | medium | 5.4 | 0% | 2026 |
| CVE-2026-76353 | medium | 5.4 | 0% | 2026 |
| CVE-2026-76347 | medium | 5.4 | 0% | 2026 |
32 older / lower-severity CVEs not shown — see Splunk Enterprise's full record.
Is my Splunk Enterprise version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Splunk Enterprise version → · Monitor Splunk Enterprise for new CVEs →
Splunk Enterprise vulnerabilities — frequently asked
How many known vulnerabilities does Splunk Enterprise have?
IsItPatched tracks 112 CVEs for Splunk Enterprise, 1 of which is actively exploited (CISA KEV). 7 are critical-severity and 39 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Splunk Enterprise have any actively-exploited vulnerabilities?
Yes — 1 Splunk Enterprise CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild. Patch it as a priority.
What is the most severe Splunk Enterprise vulnerability?
Among tracked issues, CVE-2026-20253 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Missing authentication weakness.
Is Splunk Enterprise safe to use?
It depends on the version. The latest supported Splunk Enterprise release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Splunk Enterprise security status · Splunk Enterprise end-of-life · actively-exploited CVEs. Always verify against Splunk's advisories — see our disclaimer.