cve.bz

CVE-2026-92709 rsyslog rsyslog: Path traversal

8.1 highEPSS 0.4%

High (8.1) in rsyslog rsyslog. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Rsyslog is a rocket-fast system for log processing. From versions 1.15.0 to 8.2610.0, rsyslog's omfile dynaFile facility intentionally allows templates to generate flexible output paths. This supports valid deployments that route logs into different directories or use dynamically generated file names. A deployment becomes unsafe when a dynaFile template uses a value influenced by untrusted input as a path component without explicit secure-path handling. In that configuration, the rendered path can escape the operator's intended log directory. This is not limited to the RFC5424 HOSTNAME field. Any untrusted value that reaches a dynaFile path component can create the condition. At time of publication, there are no publicly available patches.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-73 External Control of File Name or Path
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
rsyslog>= 1.15.0, <= 8.2610.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14rsyslogno fix listedDEBIAN-CVE-2026-92709
Ubuntu14.04:LTS, 22.04:LTS, 24.04:LTS and 5 morersyslogno fix listedUBUNTU-CVE-2026-92709
SUSELinux 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 morersyslog8.2306.0-150400.5.51.1SUSE-SU-2026:5122-1
SUSELinux Enterprise Module for Basesystem 15 SP7, Linux Enterprise Module for Package Hub 15 SP7, Linux Enterprise Module for Server Applications 15 SP7rsyslog8.2608.0-150700.3.29.1SUSE-SU-2026:5082-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5rsyslog8.2106.0-8.30.2SUSE-SU-2026:5089-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6rsyslog8.2406.0-150600.12.30.1SUSE-SU-2026:5100-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0rsyslog8.2608.0-160000.1.1SUSE-SU-2026:24598-1
SUSELinux Enterprise Server 16.1, Linux Enterprise Server for SAP applications 16.1rsyslog8.2608.0-160100.1.1SUSE-SU-2026:24613-1
SUSELinux Enterprise Server for NVIDIA 16.1rsyslog8.2608.0-160100.1.1SUSE-SU-2026:24697-1
openSUSELeap 16.0rsyslog8.2608.0-160000.1.1openSUSE-SU-2026:22184-1
openSUSELeap 16.1rsyslog8.2608.0-160100.1.1openSUSE-SU-2026:22293-1
openSUSETumbleweedrsyslog8.2608.0-4.1openSUSE-SU-2026:12349-1
Azure Linux3rsyslogno fix listedAZL-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

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10rsyslogAffected
Red Hat Enterprise Linux 6rsyslogAffected
Red Hat Enterprise Linux 6rsyslog7Affected
Red Hat Enterprise Linux 7rsyslogAffected
Red Hat Enterprise Linux 8rsyslogAffected
Red Hat Enterprise Linux 9rsyslogAffected

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.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON