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

Published Nov 2, 2026 CVSS 3.1 · 8.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability occurs when a CA's parent resides on the same Krill server. Instead of building and verifying a signed CMS message, Krill performs the RFC 6492 provisioning exchange in-process and blindly trusts the child identity provided by the caller. Because there is no validation that the child identity actually belongs to the CA making the request, a CA operator can assume the role of any child CA on that server.

Affected Systems

Impact applies to Krill installations running any version up to and including 0.16.0, as the issue is resolved in release 0.16.1 and later. The flaw affects all configurations where parent and child CAs coexist on the same host, regardless of operating system or architecture.

Risk and Exploitability

The CVSS score of 8.4 indicates high severity, and the EPSS score is not available, suggesting a low–to‑moderate probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. An attacker who can act as a CA operator can impersonate any child CA on the same server, enabling unauthorized certificate issuance or administrative actions. The attack vector is likely local or requires authenticated CA‑operator access to the Krill server.

Remediation

Vendor Solution

This issue is fixed in 0.16.1 and all later versions.


OpenCVE Recommended Actions

  • Upgrade to Krill 0.16.1 or newer so that child identities are validated before authorizing provisioning exchanges.
  • If an upgrade is pending, segregate parent and child CA deployments on separate servers or enforce network segmentation to prevent a single instance from hosting both roles.
  • Limit CA operator permissions and audit provisioning exchanges that involve local parents to detect and prevent unauthorized child impersonation.

Generated by OpenCVE AI on November 2, 2026 at 17:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Nlnetlabs
Nlnetlabs krill
Vendors & Products Nlnetlabs
Nlnetlabs krill
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Krill treats a "local parent" as already-authenticated, letting a CA operator act as any child of any CA on the same server
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 8.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
NLnet Labs
Published
Updated
Nov 2, 2026, 4:10 PM
Reserved
Oct 12, 2026, 11:22 AM
Status
Deferred
Published
Nov 2, 2026, 4:17 PM
Modified
Nov 2, 2026, 7:35 PM