Skip to content
major vulnerability· requires attention

Rsyslog is widely deployed on Linux servers; this high-severity path-escape can affect many orgs and enable file overwrite or data exposure.

Systems

CVE-2026-92709

8.1
High
EPSS 0.30%Patch availableOct 24, 2026

Rsyslog dynaFile templates can escape log directories and write files outside intended paths

common questions

Is CVE-2026-92709 being exploited?

Not confirmed. CVE-2026-92709 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-92709?

CVE-2026-92709 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-92709?

Yes. A fix has been recorded for CVE-2026-92709. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-92709 affect?

CVE-2026-92709 affects rsyslog 1.15.0–8.2610.0, Linux servers using rsyslog dynaFile templates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-92709?

Disable dynaFile or remove/sanitize untrusted template fields; apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
rsyslog 1.15.0–8.2610.0Linux servers using rsyslog dynaFile templates
impact

Untrusted log input can cause path traversal in dynaFile templates, allowing attacker-controlled file creation/overwrite and potential data or code compromise.

action required

Immediate action required

affected versions
rsyslog rsyslog
  • affected>= 1.15.0 and <= 8.2610.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved