Krill login-session tokens reuse their encryption nonce across restarts, so any user who can log in can forge an "admin" token
Summary
| CVE | CVE-2026-109140 |
|---|---|
| State | PUBLISHED |
| Assigner | NLnet Labs |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-02 16:17:26 UTC |
| Updated | 2026-11-02 19:35:33 UTC |
| Description | The vulnerability is that Krill encrypts every login-session token with a nonce built from a counter that is reset to 0 on every Krill restart, so the same (key, nonce) pair is used again after each restart. |
Risk And Classification
Primary CVSS: v3.1 8.4 HIGH from [email protected]
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Problem Types: CWE-323 | CWE-323 CWE-323 Reusing a Nonce, Key Pair in Encryption
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | [email protected] | Secondary | 8.4 | HIGH | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L |
| 3.1 | CNA | CVSS | 8.4 | HIGH | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
ChangedConfidentiality
HighIntegrity
HighAvailability
LowCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | NLnet Labs | Krill | unaffected 0.16.1 * semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| www.nlnetlabs.nl/downloads/krill/CVE-2026-109140.txt | [email protected] | www.nlnetlabs.nl | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: Anthropic and Ada Logics, Aymen Benlamari (en)
Additional Advisory Data
| Source | Time | Event |
|---|---|---|
| CNA | 2026-10-03T00:00:00.000Z | Issue reported |
| CNA | 2026-11-02T00:00:00.000Z | Fixes released |
Solutions
CNA: This issue is fixed in 0.16.1 and all later versions.
There are currently no legacy QID mappings associated with this CVE.