Krill users restricted to one CA can make any other CA delegate its prefixes and publish ROAs for them via bulk import
Only affects Krill up to and including 0.16.0 with users whose role is restricted to a list of CAs, which can gain bulk-import rights. 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 or later
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Krill up to and including 0.16.0 (affected versions) Attacker uses a role restricted to a list of CAs (cas = [...])
- 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 or later
- 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 software, is affected. A user whose access is limited to specific certificate authorities can bypass that restriction through the bulk import feature, letting them add child authorities under any other CA, grant those children its resources, and create route origin authorizations for them.
Read the original description
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 to a CA, including the bulk import endpoint POST /api/v1/bulk/cas/import. It adds a new child CA under any existing CA, gives the child any of that CA's resources, and creates the ROAs given in the request
What to do
Check whether your setup matches what the bug needs.
Krill up to and including 0.16.0 (affected versions) Attacker uses a role restricted to a list of CAs (cas = [...])Upgrade to a fixed version: 0.16.1 or later.
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-109141
What does this mean?
A user limited to one certificate authority (CA) in Krill can use bulk import to make any other existing CA delegate its prefixes to a new child CA. That child can then be given resources from the other CA and can publish route origin authorizations (ROAs) for them.Source: nlnetlabs.nl
Am I affected, and how do I check?
Krill up to and including 0.16.0 is affected, specifically setups where a role is restricted to a list of CAs (cas = [...]). To check, run the Krill version command and review the roles configured for CA-restricted users.Source: nlnetlabs.nl
What should I do about it?
Upgrade to Krill 0.16.1 or later, which fixes the issue.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