Krill vulnerabilities and CVEs
Known vulnerabilities affecting Krill, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.
3 vulnerabilities tracked.
- 8.4 When a CA's parent lives on the same Krill server: instead of building and verifying a signed CMS message, it runs the RFC 6492…
- 8.4 The vulnerability gives a role that is restricted to a list of CAs (cas = [...]) its full permission set for every request that is not tied…
- 8.4 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…
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Krill is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other products tracked here
Android Windows 11 version 26H1 Windows 11 Version 24H2 Windows 11 Version 25H2 Windows Server 2025 (Server Core installation) Windows Server 2025 Windows Server 2022 Windows Server 2019 (Server Core installation) Windows Server 2019 Windows 10 Version 21H2 Red Hat Enterprise Linux 9 Windows 10 Version 1809 Windows 10 Version 22H2 n/a Windows Server 2016 (Server Core installation) Windows Server 2016 Windows 10 Version 1607 Red Hat Enterprise Linux 10 Red Hat Enterprise Linux 8 Windows Server 2012 R2 (Server Core installation) Windows Server 2012 R2 macOS Windows Server 2012 (Server Core installation) Windows Server 2012