CVE-2026-104059

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

GHSA-76hh-mx5x-4xrx ↗EUVD-2026-91007 ↗

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.
lektor <= 3.3.14; >= 3.4.0b1, <= 3.4.0b15
ETK-2026-300, permanent identifier
19d 08h 11msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+11h08m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Lektor 3.3.14 and 3.4.0b15 have insufficient cross-origin request protections in the admin API. An attacker may cause administrative changes, including content, build-output, or publication actions, when a browser can access the affected admin service.

mitigation

Restrict the admin API to loopback or a trusted network and prevent untrusted websites from reaching it. Plan to move off Lektor 3.3.14 and 3.4.0b15 when a vendor-fixed release is available; the evidence does not name a fixed version.

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.
0.14%3rd percentile
agent run time
7m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 18:17Z
Δ 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-01 18:17Z
    ghsa: trigger signal, started the run
  2. 2026-10-01 18:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-300",
  "cve_id": "CVE-2026-104059",
  "display_id": "CVE-2026-104059",
  "ghsa_id": "GHSA-76hh-mx5x-4xrx",
  "euvd_id": "EUVD-2026-91007",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-site request forgery in Lektor admin API",
  "summary": "Lektor 3.3.14 and 3.4.0b15 have insufficient cross-origin request protections in the admin API. An attacker may cause administrative changes, including content, build-output, or publication actions, when a browser can access the affected admin service.",
  "mitigation": "Restrict the admin API to loopback or a trusted network and prevent untrusted websites from reaching it. Plan to move off Lektor 3.3.14 and 3.4.0b15 when a vendor-fixed release is available; the evidence does not name a fixed version.",
  "vendor": "lektor",
  "product": "lektor",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.3.14",
        ">= 3.4.0b1, <= 3.4.0b15"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "lektor",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H",
  "epss_score": 0.0014,
  "epss_percentile": 0.0305,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 6.57509595,
  "t0_at": "2026-10-01T18:17:39.168000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T18:17:39.168000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T18:17:39.168000+00:00",
      "url": "https://github.com/advisories/GHSA-76hh-mx5x-4xrx"
    }
  }
}

published 2026-10-02 05:19Z
last change 2026-10-21 09:43Z

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.