Quick answers
- Is CVE-2026-123619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123619 being exploited in the wild.
- How severe is CVE-2026-123619?
- Medium severity, with a CVSS score of 6.8, published 6 November 2026.
- Which products and versions are affected?
- Lektor through 3.3.14 and 3.4.0b15.
- Is there a fix for CVE-2026-123619?
- 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-123619 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-123619?
- 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
The vulnerability exists in Lektor's admin API on Windows, where the cleanup_path function fails to properly normalize absolute paths using drive letters (e.g., C:\). Attackers can craft requests to the deleterecord or newattachment endpoints with specially-crafted drive-letter paths to traverse outside the project directory. The attack requires network access to the local admin server but no authentication, and relies on the user having a malicious webpage open or being vulnerable to DNS rebinding.
Affected products
- Lektor Lektor through 3.3.14 and 3.4.0b15
Timeline
- 2026-11-06: disclosed