CVE-2018-11409

CRITICALNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 98% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 98%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 98%CVSS: 5.3Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

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

Splunk through 7.0.1 allows information disclosure by appending __raw/services/server/info/server-info?output_mode=json to a query, as demonstrated by discovering a license key.

CVSS v3
5.3
EG Score
9.0(high)
EG Risk
84(Track)
EG Risk 84/100SSVC: Track

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 computed
Severity90% × 45%
Exploitation98% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
98%
EPSS %ILE
100%
KEV
Not listed

Published

June 8, 2018

Last Modified

November 21, 2024

References (6)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 12× 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.

  1. 2026-07-23 01:32 UTCEG score recompute
  2. 2026-07-22 22:12 UTCEG score recompute
  3. 2026-07-19 14:28 UTCEPSS rescore
  4. 2026-07-19 02:26 UTCEPSS rescore
  5. 2026-07-19 02:26 UTCEPSS rescore
  6. 2026-07-16 16:59 UTCEPSS rescore
  7. 2026-07-16 16:59 UTCEPSS rescore
  8. 2026-07-13 22:26 UTCEPSS rescore
  9. 2026-07-12 05:43 UTCEPSS rescore
  10. 2026-07-08 15:11 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-07-01 15:03 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-22 14:23 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-10 22:16 UTCEPSS rescore
  20. 2026-06-04 13:10 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-05-31 22:29 UTCEPSS rescore
  23. 2026-05-31 22:28 UTCEPSS rescore
  24. 2026-05-31 00:14 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
Show 9 more
  1. 2026-05-28 13:42 UTCEPSS rescore
  2. 2026-05-28 13:42 UTCEPSS rescore
  3. 2026-05-28 07:06 UTCEG score recompute
  4. 2026-05-28 07:06 UTCGHSA enrichment
  5. 2026-05-27 13:38 UTCEPSS rescore
  6. 2026-05-27 13:38 UTCEPSS rescore
  7. 2026-05-26 07:17 UTCEPSS rescore
  8. 2026-05-26 07:17 UTCEPSS rescore
  9. 2026-05-26 00:16 UTCOSV refresh

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-44865
    First seen Jun 8, 2018

    Splunk < 7.0.1 - Information Disclosure

    Open source ↗
  • Metasploitauxiliary/gather/splunk_raw_server_info✓ verified
    First seen Jun 8, 2018

    Splunk __raw Server Info Disclosure

    Open source ↗
  • Nucleihttp/cves/2018/CVE-2018-11409.yaml
    First seen Jan 1, 2018

    Splunk <=7.0.1 - Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-11409?
CVE-2018-11409 is a critical vulnerability published on June 8, 2018. Splunk through 7.0.1 allows information disclosure by appending raw/services/server/info/server-info?output_mode=json to a query, as demonstrated by discovering a license key.
When was CVE-2018-11409 disclosed?
CVE-2018-11409 was first published in the National Vulnerability Database on June 8, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-11409 actively exploited?
CVE-2018-11409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
What is the CVSS score of CVE-2018-11409?
CVE-2018-11409 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2018-11409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-11409, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-11409

Explore →

Is Your Infrastructure Affected by CVE-2018-11409?

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

Start Free Scan →Browse All CVEs