CVE-2018-16866: systemd · Out-of-bounds Read
Affects systemdSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jan 2019
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Systemdsystemd/systemdpkg:rpm/systemd/systemdOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should ensure that all systems running systemd are updated to versions later than v239, where this vulnerability is fixed. Restricting local access to trusted users only and enforcing strong authentication and authorization controls will reduce the risk of exploitation. Monitoring and auditing local user activities can help detect attempts to exploit this vulnerability. Additionally, organizations should consider deploying host-based intrusion detection systems (HIDS) to identify suspicious behavior related to systemd-journald. For environments where upgrading is not immediately possible, applying strict access controls and isolating critical systems can mitigate risk. Finally, reviewing and sanitizing logs to avoid triggering the vulnerable parsing behavior may be a temporary workaround, though less practical.
Description
An out of bounds read was discovered in systemd-journald in the way it parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. Versions from v221 to v239 are vulnerable.
References
- debian.org/security/2019/dsa-4367 (opens in a new tab)
- security.netapp.com/advisory/ntap-20190117-0001/ (opens in a new tab)
- qualys.com/2019/01/09/system-down/system-down.txt (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16866 (opens in a new tab)
- usn.ubuntu.com/3855-1/ (opens in a new tab)
- securityfocus.com/bid/106527 (opens in a new tab)
- security.gentoo.org/glsa/201903-07 (opens in a new tab)
- openwall.com/lists/oss-security/2019/05/10/4 (opens in a new tab)
- seclists.org/bugtraq/2019/May/25 (opens in a new tab)
- packetstormsecurity.com/files/152841/System-Down-A-systemd-journald-Exploit.html (opens in a new tab)
- seclists.org/fulldisclosure/2019/May/21 (opens in a new tab)
- access.redhat.com/errata/RHSA-2019:2091 (opens in a new tab)
- access.redhat.com/errata/RHSA-2019:3222 (opens in a new tab)
- access.redhat.com/errata/RHSA-2020:0593 (opens in a new tab)