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

Is it exploited?

Not on CISA's list. CISA has not added it to the Known Exploited Vulnerabilities catalog as of 10 Nov 2026. If CISA adds it, this page shows it as known exploited.

How likely is exploitation in the next 30 days?

0.3%

EPSS score, percentile 20.3 of all scored records. A probability estimated by FIRST, not a report of exploitation.

How severe?

8.4 High

CVSS v3.1 base score, given by the CNA

What should I do?

This issue is fixed in 0.16.1 and all later versions.Solution from the CVE record.

CISA has set no required action, because the vulnerability is not in KEV.

Advisories and patches (1)

Which versions are affected?

Unaffected 0.16.1

Versions by product

Source: CISA KEV 2026.11.10, as of 10 Nov 2026; FIRST EPSS, as of 12 Nov 2026; CVE List, as of 12 Nov 2026. About the data.

Description

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.

Source: CVE List, as of 12 Nov 2026. About the data.

What to do

Advisories and patches

• nlnetlabs.nl (Vendor advisory)

This summary is based on the CVE record as of 12 Nov 2026. Check the vendor's advisory before you act: affected versions and fixes can change.

Affected products and versions

Source: CVE List, as of 12 Nov 2026. About the data.

Timeline