CVE-2026-92709
waiting for further signalsZero needs more public information before it can validate it.GHSA-xmp9-244p-5ggv ↗EUVD-2026-108168 ↗
description
rsyslog versions 1.15.0 through 8.2610.0 can write dynaFile output outside the intended log directory when a path template incorporates untrusted input without secure-path handling. An attacker able to influence such template data may cause log output to be directed to unintended filesystem locations; deployments without untrusted path components are not exposed to this condition.
mitigation
Review dynaFile templates now and remove untrusted fields from path components, or apply secure-path handling that confines generated paths to approved directories. Restrict who can supply log data that reaches these templates, and monitor upstream and distribution updates because no fixed version is recorded.
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-22 13:32Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-92709
{ "etk_id": "ETK-2026-2450", "cve_id": "CVE-2026-92709", "display_id": "CVE-2026-92709", "ghsa_id": "GHSA-xmp9-244p-5ggv", "euvd_id": "EUVD-2026-108168", "status": "published", "anchor_state": "anchored", "title": "Path traversal in rsyslog omfile dynaFile", "summary": "rsyslog versions 1.15.0 through 8.2610.0 can write dynaFile output outside the intended log directory when a path template incorporates untrusted input without secure-path handling. An attacker able to influence such template data may cause log output to be directed to unintended filesystem locations; deployments without untrusted path components are not exposed to this condition.", "mitigation": "Review dynaFile templates now and remove untrusted fields from path components, or apply secure-path handling that confines generated paths to approved directories. Restrict who can supply log data that reaches these templates, and monitor upstream and distribution updates because no fixed version is recorded.", "vendor": "rsyslog", "product": "rsyslog", "affected": [ { "affected_notes": [ "1.15.0 (2007-07-05) and up" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "rsyslog", "purl": null } ], "cwes": [ 22 ], "cvss_score": 8.1, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 24.053584333333333, "t0_at": "2026-10-22T13:32:56.695000+00:00", "signals": { "trigger_signal": { "at": "2026-10-22T13:32:56.695000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-22T13:32:56.695000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-92709" } } }
published 2026-10-22 14:26Z
last change 2026-10-22 16:48Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.