Skip to main content
Mallory
UnratedVulnerability

CVE-2026-129832: Local Denial of Service in rsyslog imuxsock PID Rewriting

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-129832CWE-124

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.