CVE-2026-109140

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

GHSA-7mpx-94gm-vm7j ↗EUVD-2026-115255 ↗

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.
NLnet Labs Krill
fixed in 0.16.1
CWE-323 Reusing a Nonce, Key Pair in Encryption
ETK-2026-3316Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 07msince last run
47mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+6h38m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Krill versions before 0.16.1 can reuse encryption nonces for login-session tokens after a service restart. A network attacker with existing low-level access may be able to undermine the confidentiality or integrity of affected session tokens when the same encryption key remains in use across restarts.

mitigation

Upgrade Krill to version 0.16.1 or later. Until upgrading, reduce exposure by limiting access to the Krill service and minimizing restarts.

fixed in 0.16.1

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
47m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 15:41Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-02 15:41Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3316",
  "cve_id": "CVE-2026-109140",
  "display_id": "CVE-2026-109140",
  "ghsa_id": "GHSA-7mpx-94gm-vm7j",
  "euvd_id": "EUVD-2026-115255",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Login-session token nonce reuse in Krill",
  "summary": "Krill versions before 0.16.1 can reuse encryption nonces for login-session tokens after a service restart. A network attacker with existing low-level access may be able to undermine the confidentiality or integrity of affected session tokens when the same encryption key remains in use across restarts.",
  "mitigation": "Upgrade Krill to version 0.16.1 or later. Until upgrading, reduce exposure by limiting access to the Krill service and minimizing restarts.",
  "vendor": "NLnet Labs",
  "product": "Krill",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "0.16.1"
      ],
      "package_name": "Krill",
      "purl": null
    }
  ],
  "cwes": [
    323
  ],
  "cvss_score": 8.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 47.38478333333333,
  "t0_at": "2026-11-02T15:41:58.436000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T15:41:58.436000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T15:41:58.436000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-109140"
    }
  }
}

published 2026-11-02 21:32Z
last change 2026-11-03 00:30Z

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.