CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HHigh (8.1) in rsyslog rsyslog. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-92709 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92709?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92709?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92709 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| rsyslog | >= 1.15.0, <= 8.2610.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | rsyslog | no fix listed | DEBIAN-CVE-2026-92709 |
| Ubuntu | 14.04:LTS, 22.04:LTS, 24.04:LTS and 5 more | rsyslog | no fix listed | UBUNTU-CVE-2026-92709 |
| SUSE | Linux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 5 more | rsyslog | 8.2306.0-150400.5.51.1 | SUSE-SU-2026:5122-1 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Package Hub 15 SP7, Linux Enterprise Module for Server Applications 15 SP7 | rsyslog | 8.2608.0-150700.3.29.1 | SUSE-SU-2026:5082-1 |
| SUSE | Linux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5 | rsyslog | 8.2106.0-8.30.2 | SUSE-SU-2026:5089-1 |
| SUSE | Linux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6 | rsyslog | 8.2406.0-150600.12.30.1 | SUSE-SU-2026:5100-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | rsyslog | 8.2608.0-160000.1.1 | SUSE-SU-2026:24598-1 |
| SUSE | Linux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1 | rsyslog | 8.2608.0-160100.1.1 | SUSE-SU-2026:24613-1 |
| SUSE | Linux Enterprise Server for NVIDIA 16.1 | rsyslog | 8.2608.0-160100.1.1 | SUSE-SU-2026:24697-1 |
| openSUSE | Leap 16.0 | rsyslog | 8.2608.0-160000.1.1 | openSUSE-SU-2026:22184-1 |
| openSUSE | Leap 16.1 | rsyslog | 8.2608.0-160100.1.1 | openSUSE-SU-2026:22293-1 |
| openSUSE | Tumbleweed | rsyslog | 8.2608.0-4.1 | openSUSE-SU-2026:12349-1 |
| Azure Linux | 3 | rsyslog | no fix listed | AZL-111473 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Important.
This vulnerability is rated as Important severity because exploitation can allow an unauthenticated remote entity to manipulate file paths and create or modify files with rsyslog privileges, which may lead to remote code execution. In default Red Hat Enterprise Linux installations, rsyslog routes events to fixed destination files and does not listen on the network. The flaw only poses a risk in deployments configured to dynamically generate target file paths based on untrusted log fields without sanitization.
To mitigate this issue without upgrading:
1. Audit rsyslog configurations in `/etc/rsyslog.conf` and `/etc/rsyslog.d/*.conf` for any `omfile` definitions utilizing `dynaFile` templates. Modify dynamic path templates to use fixed directories and static filenames, or apply rsyslog property-replacer regex filters to strip directory separator characters (`/` and `\`) and directory traversal sequences (`..`).
2. Restrict network access to rsyslog endpoints (UDP/TCP port 514) to trusted hosts or management networks using firewall rules:
```
firewall-cmd --permanent --remove-service=syslog
firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_SUBNET>
firewall-cmd --permanent --zone=trusted --add-port=514/tcp
firewall-cmd --permanent --zone=trusted --add-port=514/udp
firewall-cmd --reload
```
3. Restart the rsyslog daemon to apply configuration changes:
```
systemctl restart rsyslog
```
Caveats: Replacing dynamic file paths with static files will aggregate logs across hosts into shared files, which may impact existing log parsing and rotation scripts. Restarting or reloading the rsyslog service will cause a momentary interruption in log reception, during which unbuffered incoming network logs could be dropped.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | rsyslog | Affected | |
| Red Hat Enterprise Linux 6 | rsyslog | Affected | |
| Red Hat Enterprise Linux 6 | rsyslog7 | Affected | |
| Red Hat Enterprise Linux 7 | rsyslog | Affected | |
| Red Hat Enterprise Linux 8 | rsyslog | Affected | |
| Red Hat Enterprise Linux 9 | rsyslog | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92709.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.