CVE-2026-129829: Red Hat Enterprise Linux 10 · Out-of-bounds Write
Affects Red Hat Enterprise Linux 10Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 18 Nov 2026, 19:50 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.5 |
|---|
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 10rsyslog | Affected– | Fixed in– |
| Red Hat Enterprise Linux 6rsyslog | Affected– | Fixed in– |
| Red Hat Enterprise Linux 6rsyslog7 | Affected– | Fixed in– |
| Red Hat Enterprise Linux 7rsyslog | Affected– | Fixed in– |
| Red Hat Enterprise Linux 8rsyslog | Affected– | Fixed in– |
| Red Hat Enterprise Linux 9rhel9/rsyslog | Affected– | Fixed in– |
Description
The rsyslog's`imuxsock` special parser can end up writing into the received message raw buffer when trying to replace the message timestamp with the system's timestamp. A local attacker with the ability to write to the `imuxsock` socket can leverage that by crafting a malformed PRI value with a short timestamp to lead the rsyslog to perform the out-of-bounds write.