File writes via unescaped dynamic path components
Published Oct 22, 2026 · Updated Oct 22, 2026
rsyslog omfile path traversal allows attackers to write outside the intended log directory via unsafe dynaFile templates. In versions 1.15.0 through 8.2610.0, templates that insert untrusted values without secure-path handling preserve path components that escape the intended directory. Exploitation requires control over an input used by an explicitly configured template and sufficient daemon write permissions; root access and code execution are not inherent outcomes.
Summary
What happened
rsyslog omfile path traversal allows attackers to write outside the intended log directory via unsafe dynaFile templates. In versions 1.15.0 through 8.2610.0, templates that insert untrusted values without secure-path handling preserve path components that escape the intended directory. Exploitation requires control over an input used by an explicitly configured template and sufficient daemon write permissions; root access and code execution are not inherent outcomes.
The record
- CVE
- CVE-2026-92709
- Published
- Oct 22, 2026
- Updated
- Oct 22, 2026
- Vendor
- rsyslog
- Product
- rsyslog
- Classifications
- CWE-73, CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 22, 2026CVE publishedPublication date reported by the CVE source.
- Oct 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.15.0, <= 8.2610.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us