CVE-2026-92709 concerns rsyslog's omfile dynaFile facility when a dynamic file-path template incorporates untrusted input as a path component without secure path handling. Crafted input can cause the rendered output path to traverse outside the administrator-intended logging directory. The available information does not identify affected rsyslog versions, a vulnerable function, or a vendor-fixed release.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An important rsyslog omfile dynaFile path-traversal/file-write issue. In explicitly deployed configurations where an attacker can influence a value used as a dynaFile path component, rsyslog may create or append to files outside the intended log directory, constrained by its effective privileges, filesystem permissions, mandatory access controls, and sandboxing. Code execution requires additional deployment-specific conditions and is not representative of default configurations.
A critical-severity, remotely exploitable vulnerability tracked as CVE-2026-92709 affecting Debian Linux 12.0, 13.0, and 14.0. The supplied CVSS v3 vector indicates network attack vector, low complexity, no privileges or user interaction required, and high confidentiality, integrity, and availability impact.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.