# CVE-2026-104059: Lektor 3.3.14 CSRF via Admin API Endpoints

> Unauthenticated attackers can exploit CSRF in Lektor admin API to modify content, delete pages, or disclose data via malicious cross-origin requests.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-76hh-mx5x-4xrx

## What is CVE-2026-104059?

CVE-2026-104059 is a high-severity vulnerability in lektor, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Lektor 3.3.14 and 3.4.0b15 contains a cross-site request forgery vulnerability in the admin API blueprint that allows unauthenticated attackers to perform state-changing actions by sending cross-origin requests without CSRF tokens, Origin/Referer validation, CORS configuration, or Host allowlisting. Attackers can exploit the newattachment, deleterecord, build, clean, and publish endpoints from a malicious web page to write arbitrary files, delete pages, wipe build output, trigger deployment publication, and via DNS rebinding reach read endpoints to disclose data.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-104059?


## How do I fix CVE-2026-104059?

No fix has been published for CVE-2026-104059 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104059 being exploited?

There is no known exploitation of CVE-2026-104059 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104059 and fix it if it is affected.

What it is: CVE-2026-104059 is a high-severity vulnerability in lektor, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104059 in the wild and no public exploit code.

Affected product: lektor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104059/ (Markdown: https://insights.sbomify.com/CVE-2026-104059/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104059
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104059
- OSV: https://osv.dev/vulnerability/CVE-2026-104059

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104059/
Summaries are generated and may contain mistakes; the official description above is the record.