CVE-2018-16865

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. 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: 3%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute code with journald privileges. Versions through v240 are vulnerable.

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

Published

January 11, 2019

Last Modified

November 21, 2024

References (42)

Vendor Advisories for CVE-2018-16865(1)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuudev-udeb (229-4ubuntu21.15) @ xenial2026-05-27ubuntu
redhatsystemd-0:219-30.el7_3.132019-08-07redhat
redhatrhvm-appliance-0:4.2-20190129.0.el72019-02-18redhat
redhatredhat-virtualization-host-0:4.2-20190129.0.el7_62019-02-13redhat
redhatsystemd-0:219-42.el7_4.132019-02-04redhat
redhatsystemd-0:219-57.el7_5.52019-01-29redhat
redhatsystemd-0:219-62.el7_6.22019-01-14redhat

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(1)

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

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2018-16865?
CVE-2018-16865 is a high vulnerability published on January 11, 2019. An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash…
When was CVE-2018-16865 disclosed?
CVE-2018-16865 was first published in the National Vulnerability Database on January 11, 2019, 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-16865 actively exploited?
CVE-2018-16865 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-16865?
CVE-2018-16865 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2018-16865?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-16865, 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-16865

Explore →

Is Your Infrastructure Affected by CVE-2018-16865?

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

Start Free Scan →Browse All CVEs