Description
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.
Published: 2026-10-22
Score: 8.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Remote Code Execution
Action: Upgrade ASAP
AI Analysis

Impact

The vulnerability is a path traversal flaw in rsyslog's omfile dynaFile facility that allows an attacker to inject arbitrary output paths derived from untrusted input. When a dynaFile template incorporates such input without explicit secure-path handling, the rendered file path can escape the operator's intended directory, enabling an arbitrary file write with the privileges of the rsyslog process. If the process runs as root, this can lead to remote code execution.

Affected Systems

Affected systems include the rsyslog software platform from version 1.15.0 through 8.2610.0. These releases support dynamic output paths via the dynaFile facility, and the flaw exists on all operating systems where rsyslog is installed, such as Linux distributions, FreeBSD, and OpenBSD. Any configuration that uses dynaFile templates with untrusted fields is vulnerable.

Risk and Exploitability

The CVSS score of 8.1 indicates a high severity condition. The EPSS score is not available, and the vulnerability is not yet listed in the CISA KEV catalog. The likely attack vector involves an adversary sending a crafted syslog message that contains a template value derived from untrusted data, such as a HOSTNAME or other field, which rsyslog processes. This can be performed remotely via any protocol that rsyslog accepts log data over, or locally where a compromised user can influence log input.

Generated by OpenCVE AI on October 22, 2026 at 15:20 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a patched rsyslog release as soon as it becomes available, or revert to a version prior to 1.15.0 or after 8.2610.0 if a fix is included.
  • Temporarily disable the dynaFile facility or configure it to use only explicit, validated filenames, enforcing the secure_path option or removing untrusted template variables from the path.
  • Ensure that all template values used in dynaFile paths originate from trusted sources; sanitize or escape any exported fields such as HOSTNAME before injecting them into the path.
  • Consider isolating rsyslog into a dedicated container or chroot with minimal permissions, limiting the rsyslog process to write only to the intended log directory, to reduce the impact if an arbitrary file write is achieved.

Generated by OpenCVE AI on October 22, 2026 at 15:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 29 Oct 2026 03:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 23 Oct 2026 00:45:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Important


Thu, 22 Oct 2026 14:30:00 +0000

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

Thu, 22 Oct 2026 13:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Rsyslog: DynFile Path Traversal → Arbitrary File Write as Root → RCE
Weaknesses CWE-22
CWE-73
References
Metrics cvssV3_1

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


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-29T02:15:30.165Z

Reserved: 2026-09-16T16:22:31.542Z

Link: CVE-2026-92709

cve-icon Vulnrichment

Updated: 2026-10-29T02:15:22.521Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-22T14:17:51.473

Modified: 2026-10-29T04:18:43.610

Link: CVE-2026-92709

cve-icon Redhat

Severity : Important

Publid Date: 2026-10-22T13:32:56Z

Links: CVE-2026-92709 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-22T15:30:08Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-73

    External Control of File Name or Path