SecurityFan score 22 · Tier C3 sources
Re: rsyslog >=8.3.2: low-year weekday formatting can crash rsyslogd (GHSA-5pc2-f2v7-5w5p)
The Brief · written from 3 sources
- Three rsyslog advisories were posted to the oss-security list on 2026-11-17, covering a crash in low-year weekday formatting (GHSA-5pc2-f2v7-5w5p) and two imuxsock memory-safety bugs in the system-timestamp and TAG parsing code.
- The weekday formatting issue can crash rsyslogd in versions 8.3.2 and later.
- The imuxsock flaws are an out-of-bounds read and an out-of-bounds write that a local sender can trigger; the write can go beyond a received message's raw buffer.
Why it matters
Any system running rsyslog 8.3.2 or later may have rsyslogd crash, and local senders can reach memory-safety bugs in the imuxsock input, so logging infrastructure should be checked against the advisories.
Who’s affected
- rsyslog users on version 8.3.2 and later
- Systems using the rsyslog imuxsock input
- rsyslog >=8.3.2
- #rsyslog
- #logging
- #security
- #memory-safety
- #linux
Posted by Rainer Gerhards on Nov 17 Apologies: the source patch was inadvertently omitted from my previous message. We use supervised AI assistance to handle the current volume of coordinated GHSA work and catch up with reporting. This omission nevertheless passed through my own…
Timeline
Full coverage · 3 sources
- 8h ago ↗
Open Source Security
rsyslog imuxsock TAG parser out-of-bounds read - 8h ago ↗
Open Source Security
rsyslog imuxsock system-timestamp out-of-bounds write - 9h ago ↗
Open Source Security
Re: rsyslog >=8.3.2: low-year weekday formatting can crash rsyslogd (GHSA-5pc2-f2v7-5w5p)