Quick answers
- Is CVE-2026-75418 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75418 being exploited in the wild.
- How severe is CVE-2026-75418?
- High severity, with a CVSS score of 7.5, published 28 August 2026.
- Which products and versions are affected?
- Lektor <3.3.14.
- Is there a fix for CVE-2026-75418?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75418 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-75418?
- Check whether you run Lektor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in Lektor's built-in preview/development web server that fails to properly sanitize HTTP request paths containing traversal sequences (such as ../ or ..\). An attacker with network access can craft HTTP requests to bypass path restrictions and read files outside the intended directory. The vulnerability is specific to Windows systems in versions before 3.3.14. Exploitation requires only network access to the preview server; no authentication is needed. An attacker can disclose arbitrary files accessible to the Lektor process, including deployment configurations and credentials. A patch is available in Lektor 3.3.14 and later.
Affected products
- Lektor Lektor <3.3.14
Timeline
- 2026-08-28: disclosed
- other: Proof-of-concept available on GitHub