CVE-2026-129832: Local Denial of Service in rsyslog imuxsock PID Rewriting
CVE-2026-129832 is a buffer-underwrite vulnerability in the PID-rewriting path of rsyslog's imuxsock module, affecting versions starting at 5.7.1 before the fix. When UsePIDFromSystem or SysSock.UsePIDFromSystem is enabled, a message with an empty TAG causes fixPID() to calculate an offset of -1 and copy the PID suffix starting one byte before the stack-allocated TAG buffer. This out-of-bounds write can terminate rsyslogd, causing local denial of service. The vulnerable path requires SCM_CREDENTIALS support and imuxsock's special parser.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A local sender with write access to the affected Unix datagram socket can crash rsyslogd and repeatedly interrupt log processing. Termination has been demonstrated against a fortified release build. No confidentiality loss, integrity loss, or code execution has been demonstrated. The vulnerability is rated Medium with CVSS 3.1 score 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Mitigation
If you can’t patch tonight, do this now.
Keep UsePIDFromSystem and SysSock.UsePIDFromSystem disabled; both options are disabled by default. If PID rewriting must remain enabled, restrict write access to the affected imuxsock Unix datagram socket to trusted senders.
Remediation
Patch, then assume compromise.
Upgrade to the rsyslog 2026-11-17 daily stable release or a subsequent release containing the fix, or apply the upstream fix associated with advisory GHSA-6rqh-v5w3-r7h4. The fix bounds the backward scan to parsed TAG bytes and safely appends the PID when the TAG is empty while preserving existing PID handling, trailing-colon behavior, and buffer-capacity checks.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-129832 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-129832 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-129832?
- As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-129832.
- Is there a patch for CVE-2026-129832?
- Upgrade to the rsyslog 2026-11-17 daily stable release or a subsequent release containing the fix, or apply the upstream fix associated with advisory GHSA-6rqh-v5w3-r7h4. The fix bounds the backward scan to parsed TAG bytes and safely appends the PID when the TAG is empty while preserving existing PID handling, trailing-colon behavior, and buffer-capacity checks.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.