CVE-2018-17246

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 82%
CISA-KEV: Not listedEPSS: 82%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. An attacker with access to the Kibana Console API could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with permissions of the Kibana process on the host system.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
99.6%
KEV
Not listed

Published

December 20, 2018

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jun 7, 2026
Patch available. Sources: redhat.
generic

Product Security at Elastic | Elastic

https://www.elastic.co/community/security
generic

Elastic Stack 6.4.3 and 5.6.13 security update - Security Announcements - Discuss the Elastic Stack

https://discuss.elastic.co/t/elastic-stack-6-4-3-and-5-6-13-security-update/155594

Vendor Advisories for CVE-2018-17246(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-monitor-sample-app-0:3.11.51-1.git.5.f6d0188.el72018-12-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 26× 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-09 19:06 UTCEPSS rescore
  2. 2026-07-07 13:42 UTCEPSS rescore
  3. 2026-07-07 13:42 UTCEPSS rescore
  4. 2026-07-04 06:28 UTCEPSS rescore
  5. 2026-07-03 20:26 UTCOSV refresh
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-21 14:54 UTCEPSS rescore
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-21 01:57 UTCEPSS rescore
  16. 2026-06-21 01:57 UTCEPSS rescore
  17. 2026-06-18 17:50 UTCEPSS rescore
  18. 2026-06-18 17:50 UTCEPSS rescore
  19. 2026-06-17 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-16 17:50 UTCEPSS rescore
  22. 2026-06-16 17:50 UTCEPSS rescore
  23. 2026-06-15 17:45 UTCEPSS rescore
  24. 2026-06-15 08:43 UTCOSV refresh
  25. 2026-06-13 22:58 UTCEPSS rescore
Show 14 more
  1. 2026-06-13 22:58 UTCEPSS rescore
  2. 2026-06-08 14:14 UTCEPSS rescore
  3. 2026-06-08 14:14 UTCEPSS rescore
  4. 2026-06-02 20:11 UTCEPSS rescore
  5. 2026-06-02 20:11 UTCEPSS rescore
  6. 2026-06-01 13:49 UTCEPSS rescore
  7. 2026-05-31 22:29 UTCEPSS rescore
  8. 2026-05-31 22:28 UTCEPSS rescore
  9. 2026-05-29 13:41 UTCEPSS rescore
  10. 2026-05-28 00:05 UTCEG score recompute
  11. 2026-05-28 00:05 UTCVendor advisory
  12. 2026-05-28 00:05 UTCGHSA enrichment
  13. 2026-05-26 07:17 UTCEPSS rescore
  14. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(2 references)

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

  • GitHub PoCmpgn/CVE-2018-17246
    First seen Mar 8, 2019

    CVE-2018-17246 - Kibana LFI < 6.4.3 & 5.6.13

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

    Kibana - Local File Inclusion

    Open source ↗

Frequently asked(5)

What is CVE-2018-17246?
CVE-2018-17246 is a critical vulnerability published on December 20, 2018. Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. An attacker with access to the Kibana Console API could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with…
When was CVE-2018-17246 disclosed?
CVE-2018-17246 was first published in the National Vulnerability Database on December 20, 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-17246 actively exploited?
CVE-2018-17246 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-17246?
CVE-2018-17246 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-17246?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-17246, 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-17246

Explore →

Is Your Infrastructure Affected by CVE-2018-17246?

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