CVE-2026-115353

waiting for further signalsZero needs more public information before it can validate it.

GHSA-9jjx-3hq3-hx4j ↗EUVD-2026-108422 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
lepture mistune <= 3.2.1
fixed in 3.3.0
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-2494Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/mistune
1h 26msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h29m
0
+4h
+6h
+8h
+10h
+12h

description

Mistune versions earlier than 3.3.0 are affected by path traversal in RST include processing. An attacker who can supply content for rendering may cause the renderer to incorporate readable local files when include directives are processed.

mitigation

Upgrade mistune to version 3.3.0 or later. Until upgrading, do not render untrusted content with RST include directives enabled.

fixed in 3.3.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 19:13Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

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.

  1. 2026-10-22 19:13Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-115353

{
  "etk_id": "ETK-2026-2494",
  "cve_id": "CVE-2026-115353",
  "display_id": "CVE-2026-115353",
  "ghsa_id": "GHSA-9jjx-3hq3-hx4j",
  "euvd_id": "EUVD-2026-108422",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Mistune RST include handling",
  "summary": "Mistune versions earlier than 3.3.0 are affected by path traversal in RST include processing. An attacker who can supply content for rendering may cause the renderer to incorporate readable local files when include directives are processed.",
  "mitigation": "Upgrade mistune to version 3.3.0 or later. Until upgrading, do not render untrusted content with RST include directives enabled.",
  "vendor": "lepture",
  "product": "mistune",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.2.1"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.3.0"
      ],
      "package_name": "mistune",
      "purl": "pkg:pypi/mistune"
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 7.712077533333333,
  "t0_at": "2026-10-22T19:13:30.422000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T19:13:30.422000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T19:13:30.422000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-115353"
    }
  }
}

published 2026-10-22 20:34Z
last change 2026-10-22 22:05Z

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.