Live › vulnerability › CVE-2026-109140
Krill encrypts each login-session token with a nonce from a counter that resets to 0 on every restart, so the same key and nonce pair is reused. Reused nonces can let an attacker recover session token contents or forge valid tokens.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 16:24 UTC. All times on this page are UTC.
Anyone running Krill (NLnet Labs' RPKI certificate authority software) up to and including 0.16.0 with login users. The vendor says any user who can log in can forge an admin session token, so the risk is mainly from accounts that are not meant to be admins. Teams not running Krill can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| krill | vendor | <= 0.16.0 | 0.16.1 |
Run krill --version (or krillc --version). Krill 0.16.0 and earlier is affected; 0.16.1 or later is fixed. Distribution packages may differ, so check the package changelog.
Install Krill 0.16.1 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-109140")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.