Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-22T13:32:56.695Z
Reserved: 2026-09-16T16:22:31.542Z
Link: CVE-2026-92709
No data.
Status : Received
Published: 2026-10-22T14:17:51.473
Modified: 2026-10-22T14:17:51.473
Link: CVE-2026-92709
No data.
OpenCVE Enrichment
Updated: 2026-10-22T15:30:08Z