Description
A flaw was found in rsyslog. When using the imdtls input module configured for name or fingerprint authentication, permitted-peer identity checks are not enforced after a successful DTLS handshake. A remote attacker possessing a valid certificate signed by the listener's trusted Certificate Authority could bypass peer restrictions and inject unauthorized syslog records into the input stream.
Published: n/a
Score: 3.1 Low
EPSS: n/a
KEV: No
Impact: Unauthorized injection of syslog records via authentication bypass
Action: Assess Impact
AI Analysis

Impact

A flaw in rsyslog’s imdtls input module allows a remote attacker to bypass permitted‑peer identity checks after a successful DTLS handshake. If the attacker presents a certificate signed by a certificate authority trusted by the rsyslog listener, the verified peer identity is not checked and the attacker may inject arbitrary syslog messages into the input stream. The weakness is an authentication failure (CWE‑287) that enables unauthorized data injection and can lead to tampered logs, stealthy operations, or data exfiltration.

Affected Systems

The vulnerability affects installations of rsyslog that use the imdtls input module configured for name or fingerprint authentication. No specific product versions are listed, but any rsyslog deployment that enables this configuration is potentially impacted.

Risk and Exploitability

The CVSS score of 3.1 indicates low base severity, and the EPSS score is unavailable. The flaw is not yet listed in the CISA KEV catalog, suggesting limited evidence of exploitation. Nonetheless, the attack vector is remote over a network connection that uses DTLS, and the attacker must have a valid certificate from a trusted CA. The risk is that authenticated peers are effectively ignored, granting an attacker the ability to inject unauthorized logs into the system.

Generated by OpenCVE AI on September 30, 2026 at 01:54 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update rsyslog to a version where the imdtls permitted‑peer checks are enforced after DTLS handshakes.
  • If an update is not possible, disable name or fingerprint authentication for the imdtls module or remove the module entirely from the configuration.
  • Limit external access to the rsyslog listening port via firewalling or network segmentation so that only trusted hosts can establish DTLS connections.

Generated by OpenCVE AI on September 30, 2026 at 01:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 29 Sep 2026 17:30:00 +0000

Type Values Removed Values Added
First Time appeared Rsyslog
Rsyslog rsyslog
Vendors & Products Rsyslog
Rsyslog rsyslog

Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
Description A flaw was found in rsyslog. When using the imdtls input module configured for name or fingerprint authentication, permitted-peer identity checks are not enforced after a successful DTLS handshake. A remote attacker possessing a valid certificate signed by the listener's trusted Certificate Authority could bypass peer restrictions and inject unauthorized syslog records into the input stream.
Title rsyslog: rsyslog: imdtls permitted-peer authorization bypass
Weaknesses CWE-287
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}

threat_severity

Low


cve-icon MITRE

No data.

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Low

Publid Date: 2026-09-22T16:00:00Z

Links: CVE-2026-93402 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-30T02:00:15Z

Weaknesses