# CVE-2026-92709: Rsyslog: DynFile Path Traversal → Arbitrary File Write as Root → RCE


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-111473, DEBIAN-CVE-2026-92709, ECHO-66b7-0f22-7b10, GHSA-xmp9-244p-5ggv, UBUNTU-CVE-2026-92709

## What is CVE-2026-92709?

CVE-2026-92709 is a high-severity vulnerability in rsyslog, published on 22 Oct 2026. 

### Official 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.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-92709?


## How do I fix CVE-2026-92709?

No fix has been published for CVE-2026-92709 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92709 being exploited?

There is no known exploitation of CVE-2026-92709 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92709 and fix it if it is affected.

What it is: CVE-2026-92709 is a high-severity vulnerability in rsyslog, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92709 in the wild and no public exploit code.

Affected product: rsyslog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92709/ (Markdown: https://insights.sbomify.com/CVE-2026-92709/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92709
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92709
- OSV: https://osv.dev/vulnerability/CVE-2026-92709

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92709/
Summaries are generated and may contain mistakes; the official description above is the record.