Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-129829

Rsyslog: rsyslog's imuxsock special parser can write beyond a received message's raw buffer when replacing the message timestamp

No exploitation reported by the sources we read.

  • Published2026-11-18
  • WeaknessCWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1819:32CVE publishedCNA

Versions per branch

Products declared by the CNA7 products

As redhat, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

1 more product in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-18

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • rsyslogUbuntu:Pro:20.04:LTSall versions · no fixed version listed
  • rsyslogUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • rsyslogUbuntu:Pro:16.04:LTSall versions · no fixed version listed
  • rsyslogUbuntu:26.10all versions · no fixed version listed
  • rsyslogUbuntu:26.04:LTSall versions · no fixed version listed
  • rsyslogUbuntu:24.04:LTSall versions · no fixed version listed
  • rsyslogUbuntu:22.04:LTSall versions · no fixed version listed
  • rsyslogUbuntu:14.04:LTSall versions · no fixed version listed

4 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-11-19
  • CISA-ADPSSVC decisionnone2026-11-19
  • CNACVSS 3.15.52026-11-18
  • CNAweakness (CWE)CWE-7872026-11-18
  • OSVaffected packages—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Published
2026-11-18
Last Modified
2026-11-19
NVD status
Awaiting Analysis

Frequently asked questions

What is CVE-2026-129829?

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.

Is CVE-2026-129829 actively exploited?

Active exploitation of CVE-2026-129829 has not been confirmed.

What is the CVSS score for CVE-2026-129829?

CVE-2026-129829 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Running rsyslog? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record