CVE-2026-129837: rsyslog weekday-name formatting out-of-bounds read
CVE-2026-129837 is an out-of-bounds read in rsyslog affecting upstream v8 releases starting with 8.3.2, prior to the fix. The RFC5424 timestamp parser accepts low-year timestamps, including year 0001, for which getWeekdayNbr can return a negative weekday remainder. The date-wdayname formatter uses that value to index a seven-element weekday-name table, causing an out-of-bounds read and potentially terminating rsyslogd. A single crafted message received through imtcp and processed by an affected action template reproduced a SIGSEGV in a normal build. The related date-wday formatter can produce invalid numeric output.
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.
An unauthenticated remote attacker can crash rsyslogd and disrupt log processing when a reachable input accepts the crafted message and routes it through the affected template. Testing demonstrated an eight-byte global out-of-bounds read and process termination, but not unrelated memory disclosure or integrity compromise. The configuration-dependent denial of service is rated CVSS v3.1 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Mitigation
If you can’t patch tonight, do this now.
Until a fix is installed, avoid date-wdayname and date-wday formatting of untrusted reported timestamps, or restrict access to affected inputs to trusted senders. Assess exposure using the actual input, routing, and action-template configuration.
Remediation
Patch, then assume compromise.
Install a verified upstream or distribution fix. The identified fixed upstream label is "2026-11-17 daily stable"; verify source, release, and binary-package availability separately. The source correction updates getWeekdayNbr to add seven when the weekday remainder is negative, normalizing it before table indexing. Downstream maintainers and administrators should verify the applied source changes, backports, and deployed rsyslogd binary rather than relying solely on the upstream version number.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-129837 exploited in the wild?
- As of Nov 18, 2026, Mallory has no reports of CVE-2026-129837 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-129837?
- As of Nov 18, 2026, Mallory has found no public exploit for CVE-2026-129837.
- Is there a patch for CVE-2026-129837?
- Install a verified upstream or distribution fix. The identified fixed upstream label is "2026-11-17 daily stable"; verify source, release, and binary-package availability separately.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.