CVE-2026-129834: Permitted-peer authentication bypass in rsyslog imdtls
CVE-2026-129834 is a certificate-based peer authentication bypass in rsyslog's optional imdtls input, affecting upstream versions starting with 8.2402.0 before the fix. When tls.authmode is set to name or fingerprint and tls.permittedpeer is configured, a client possessing a CA-signed but non-permitted certificate can pace the final DTLS handshake flight so that the handshake completes during SSL_read. This execution path processes application data without performing the manual permitted-peer check, allowing an otherwise unauthorized client to submit data.
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 attacker possessing a CA-signed but non-permitted client certificate can bypass configured peer restrictions and inject unauthorized log messages, compromising log integrity. The vulnerability has a conditional Medium CVSS v3.1 score of 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). No direct confidentiality or availability impact is established for this specific vulnerability; the related listener-stalling issues have separate CVE identifiers.
Mitigation
If you can’t patch tonight, do this now.
Until the fix is installed, restrict network access to exposed imdtls inputs to authorized clients and tightly control client-certificate issuance.
Remediation
Patch, then assume compromise.
Upgrade to a fixed rsyslog build incorporating the fix included in the November 17, 2026 daily stable release, or apply the shared production patch associated with advisory GHSA-4chq-f2r9-5jp8 and rsyslog pull request 8022. The common patch addresses CVE-2026-129834, CVE-2026-129835, and CVE-2026-129836 and should be applied once rather than as separate patches. Verify distribution package availability and inclusion of the fix independently of upstream source or release availability.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-129834 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-129834 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-129834?
- As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-129834.
- Is there a patch for CVE-2026-129834?
- Upgrade to a fixed rsyslog build incorporating the fix included in the November 17, 2026 daily stable release, or apply the shared production patch associated with advisory GHSA-4chq-f2r9-5jp8 and rsyslog pull request 8022. The common patch addresses CVE-2026-129834, CVE-2026-129835, and CVE-2026-129836 and should be applied once rather than as separate patches.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.