CVE-2026-109142
Krill treats a "local parent" as already-authenticated, letting a CA operator act as any child of any CA on the same server
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 provisioning exchange in-process and trusts the child identity (child_handle) that the caller put in the parent contact. Nothing checks that this child identity actually belongs to the CA making the request.
Fixes and workarounds
Fix
This issue is fixed in 0.16.1 and all later versions.
Source: CNA: NLnet LabsAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Krill NLnet Labs |
≥ 0.16.1; < * (unaffected, semver)
Other versions: affected |
CNA: NLnet Labs |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.4 high |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L | CNA: NLnet Labs |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.nlnetlabs.nl/downloads/krill/CVE-2026-109142.txtCNA: NLnet Labs · vendor-advisory
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.