CVE-2026-109140
HighCVSS 8.4Summary
Krill encrypts every login-session token with a nonce built from a counter that is reset to 0 on every restart, so the same (key, nonce) pair is reused after each restart.
Risk Assessment
Reusing a (key, nonce) pair in encryption weakens session token confidentiality and may enable decryption or impersonation. This violates fundamental cryptographic security assumptions.
Recommendation
Update Krill to a version with the fix that ensures nonce uniqueness. Until then, consider invalidating sessions after a service restart.
Other vulnerabilities in Krill
See all- CVE-2026-109142High
In Krill, when a parent CA lives on the same server, the RFC 6492 provisioning exchange runs in-process instead of building and verifying a signed CMS message. The child identity (child_handle) supplied by the caller in the parent contact is trusted without verifying that it actually belongs to the requesting CA.
- CVE-2026-109141High
A role restricted to a list of CAs (cas = [...]) receives its full permission set for requests not tied to a CA, including the bulk import endpoint POST /api/v1/bulk/cas/import. This allows adding a new child CA under any existing CA, assigning it any of that CA's resources, and creating the ROAs specified in the request.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS