Public vulnerability disclosure

CVE-2026-63121

Kubewarden trusted-repos-policy: uppercase registry host bypasses registry/image deny rules

publishedCWE-178

Kubewarden policies is a collection of WebAssembly policies for securing and governing Kubernetes clusters. For versions provisionally classified as affected before 2.1.2, `trusted-repos-policy` compares an image's `registry` hostname against `reject lists` and `allow lists` case-sensitively even though `registry` DNS names are case-insensitive. An image with an uppercase or mixed-case `registry` hostname can miss a rejection rule for the equivalent lowercase host, so the admission policy accepts a resource whose container runtime pulls the same prohibited image. Only reject-list configurations have this bypass: allow-list configurations fail closed by over-denying differently cased hostnames. The security consequences depend on the configured rejection policy and deployment environment. This issue is fixed in version 2.1.2.

Technical severity6.3 mediumCVSS 3.1 · CNA: GitHub_M
Published2026-10-30Source updated 2026-11-05
Collected2026-11-054 attributed sources

Fixes and workarounds

Fix

trusted-repos-policy (kubewarden): GitHub reports patched versions 2.1.2. Check the advisory for the affected release branch.

Source: GitHub GHSA-8p62-9vh2-272p

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
policies
kubewarden
< 2.1.2 (affected) CNA: GitHub_M
trusted-repos-policy

trusted-repos-policy
kubewarden
2.1.1 (affected, GitHub advisory range) GitHub GHSA-8p62-9vh2-272p

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 6.3
medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:LCNA: GitHub_M
3.1 / 6.3
medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:LNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

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/cves
https://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.

Agent access JSON · OpenAPI · CVE API guide