Directory Traversal Affecting rsyslog package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.45% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-RSYSLOG-20067666
  • published24 Sept 2026
  • disclosed22 Oct 2026

Introduced: 24 Sep 2026

NewCVE-2026-92709  (opens in a new tab)
CWE-22  (opens in a new tab)
CWE-73  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable rsyslog.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rsyslog package and not the rsyslog package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1