Krill treats a "local parent" as already-authenticated, letting a CA operator act as any child of any CA on the same server
Affects Krill up to and including 0.16.0 when a CA's parent is hosted on the same Krill server. Fixed in 0.16.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.16.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The CA's parent is hosted on the same Krill server (local parent). Affected versions are Krill up to and including 0.16.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.16.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Krill, the open-source Resource Public Key Infrastructure (RPKI) Certificate Authority server, is affected. A CA operator on a Krill server can impersonate any child of any other CA hosted on that same server, allowing them to act on resources they should not control.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
The CA's parent is hosted on the same Krill server (local parent). Affected versions are Krill up to and including 0.16.0.Upgrade to a fixed version: 0.16.1.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- NLnet Labs Krill
Version range not reported
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-109142
What does this mean?
Krill treats a CA's parent that runs on the same server as already authenticated. A CA operator can use this to act as any child of any CA on that server.Source: nlnetlabs.nl
Am I affected, and how do I check?
Krill up to and including 0.16.0 is affected, but only when a CA's parent is hosted on the same Krill server (a local parent). Check your Krill version and whether any CA's parent is configured on the same server.Source: nlnetlabs.nl
What should I do about it?
Install Krill 0.16.1 or later.Source: nlnetlabs.nl
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: cve.now feed data