CVE-2018-9401

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-01-18. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

In many locations, there is a possible way to access kernel memory in user space due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
0.8%
KEV
Not listed

Published

January 18, 2025

Last Modified

July 10, 2025

References (1)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 30× 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-22 22:18 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-20 17:04 UTCEPSS rescore
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-16 16:59 UTCEPSS rescore
  6. 2026-07-16 16:59 UTCEPSS rescore
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-15 01:56 UTCEPSS rescore
  9. 2026-07-13 22:27 UTCEPSS rescore
  10. 2026-07-13 06:10 UTCEPSS rescore
  11. 2026-07-12 05:43 UTCEPSS rescore
  12. 2026-07-09 19:06 UTCEPSS rescore
  13. 2026-07-08 15:11 UTCEPSS rescore
  14. 2026-07-08 15:11 UTCEPSS rescore
  15. 2026-07-07 13:42 UTCEPSS rescore
  16. 2026-07-07 13:42 UTCEPSS rescore
  17. 2026-07-06 16:25 UTCEPSS rescore
  18. 2026-07-06 16:24 UTCEPSS rescore
  19. 2026-07-04 06:28 UTCEPSS rescore
  20. 2026-07-04 06:28 UTCEPSS rescore
  21. 2026-06-30 23:20 UTCEPSS rescore
  22. 2026-06-30 23:20 UTCEPSS rescore
  23. 2026-06-29 14:03 UTCEPSS rescore
  24. 2026-06-28 14:04 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 39 more
  1. 2026-06-25 13:47 UTCEPSS rescore
  2. 2026-06-24 14:02 UTCEPSS rescore
  3. 2026-06-24 14:02 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-18 17:50 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-16 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-14 23:15 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-11 13:57 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-10 13:19 UTCEPSS rescore
  22. 2026-06-08 14:14 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 22:45 UTCEPSS rescore
  26. 2026-06-05 22:45 UTCEPSS rescore
  27. 2026-06-05 06:08 UTCEPSS rescore
  28. 2026-06-05 06:08 UTCEPSS rescore
  29. 2026-06-04 13:10 UTCEPSS rescore
  30. 2026-06-04 13:10 UTCEPSS rescore
  31. 2026-06-02 20:11 UTCEPSS rescore
  32. 2026-06-01 13:50 UTCEPSS rescore
  33. 2026-05-31 22:29 UTCEPSS rescore
  34. 2026-05-31 22:29 UTCEPSS rescore
  35. 2026-05-31 00:14 UTCEPSS rescore
  36. 2026-05-31 00:14 UTCEPSS rescore
  37. 2026-05-30 13:08 UTCEG score recompute
  38. 2026-05-30 13:08 UTCGHSA enrichment
  39. 2026-05-29 13:41 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-9401?
CVE-2018-9401 is a high vulnerability published on January 18, 2025. In many locations, there is a possible way to access kernel memory in user space due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2018-9401 disclosed?
CVE-2018-9401 was first published in the National Vulnerability Database on January 18, 2025, with the most recent update on July 10, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-9401 actively exploited?
CVE-2018-9401 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-9401?
CVE-2018-9401 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2018-9401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-9401, 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-9401

Explore →

Is Your Infrastructure Affected by CVE-2018-9401?

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

Start Free Scan →Browse All CVEs