CVE-2026-29111VulnerabilityPublished 19 May 2026Updated 30 Oct 2026

Red Hat Security Advisory: systemd security update

Affects Red Hat systemdSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 06:59 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

bundesamt-f-r-sicherheit-in-de

What to do

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=9.0 <=9.8 >=10.0 <=10.2 Red Hat Red Hat Enterprise Linux Red Hat Enterprise Linux AppStream (v. 10) Red Hat Enterprise Linux BaseOS (v. 10) x86_64 Red Hat Enterprise Linux AppStream (v. 9) Red Hat Enterprise Linux BaseOS (v. 9) aarch64 noarch Red Hat Enterprise Linux AppStream EUS (v. 10.0) Red Hat Enterprise Linux BaseOS EUS (v. 10.0) Red Hat Enterprise Linux AppStream EUS (v.9.6) Red Hat Enterprise Linux BaseOS EUS (v.9.6) Red Hat Enterprise Linux BaseOS E4S (v.8.8) Red Hat Enterprise Linux BaseOS TUS (v.8.8) src Red Hat Enterprise Linux BaseOS AUS (v.8.6) Red Hat Enterprise Linux BaseOS EUS EXTENSION (v.8.6) Red Hat Enterprise Linux BaseOS AUS (v.8.4) Red Hat Enterprise Linux BaseOS EUS EXTENSION (v.8.4) i686 Red Hat Enterprise Linux AppStream E4S (v.9.4) Red Hat Enterprise Linux BaseOS E4S (v.9.4) Red Hat Enterprise Linux AppStream E4S (v.9.2) Red Hat Enterprise Linux BaseOS E4S (v.9.2) SUSE libsystemd0-257.13-160000.1.1.aarch64 libudev1-257.13-160000.1.1.aarch64 systemd-257.13-160000.1.1.aarch64 systemd-0:252-51.el9_6.6.i686 systemd-container-0:252-51.el9_6.6.i686 systemd-devel-0:252-51.el9_6.6.i686 libsystemd0-0:257.13-160000.1.1.aarch64 libudev1-0:257.13-160000.1.1.aarch64 systemd-0:257.13-160000.1.1.aarch64	Fixed in–

AI-suggested

Red Hat has released official security updates for systemd that address CVE-2026-29111. Users should apply the provided updates for Red Hat Enterprise Linux versions 9.0 through 9.8 and 10.0 through 10.2 as detailed in Red Hat advisories RHSA-2026:13651 and RHSA-2026:13677. Refer to https://access.redhat.com/articles/11258 for update instructions. No additional mitigation steps are indicated beyond applying the official patches.

Description

The systemd packages contain systemd, a system and service manager for Linux, compatible with the SysV and LSB init scripts. It provides aggressive parallelism capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, and keeps track of processes using Linux cgroups. In addition, it supports snapshotting and restoring of the system state, maintains mount and automount points, and implements an elaborate transactional dependency-based service control logic. It can also work as a drop-in replacement for sysvinit. Security Fix(es): * systemd: systemd: Arbitrary code execution or Denial of Service via spurious IPC API call data (CVE-2026-29111) Bug Fix(es) and Enhancement(s): * spec: systemd build fails due to rename of rhel-net-naming-sysattrs upstream (JIRA:RHEL-150625) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

Successful exploitation of this vulnerability could allow an attacker to execute arbitrary code or cause a denial of service on affected systems running vulnerable versions of systemd. This could disrupt system operations or compromise system integrity. The severity is rated moderate by Red Hat Product Security.

Summary

The systemd packages in Red Hat Enterprise Linux contain a vulnerability identified as CVE-2026-29111, which permits arbitrary code execution or denial of service triggered by spurious IPC API call data. Systemd is a critical component managing system and service initialization and control, including process tracking via Linux cgroups and socket/D-Bus activation. The vulnerability impacts multiple Red Hat Enterprise Linux versions (9.x and 10.x) and architectures (x86_64, aarch64, ppc64le, s390x). Red Hat has released updated systemd packages to fix this issue, as documented in their security advisories RHSA-2026:13651 and RHSA-2026:13677.

CWE-1287Improper Validation of Specified Type of Input (opens in a new tab)
Base weakness
The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 16:22 UTC

WeaknessesCWE-1287

Technical details

References

Community reviews

Related threats