CVE-2026-63121

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

CVSS score

6.3

EPSS probability

—

Risk score

0.6

Published

2 h ago

Overview Public Exploits (0)Newsroom Vulnerability Timeline

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

Kubewarden trusted-repos-policy Uppercase Registry Host Bypass Vulnerability

Sources read

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

The trusted-repos-policy component within Kubewarden policies compares registry hostnames case-sensitively. S0

Why does it matter?

Uppercase or mixed-case registry hostnames can bypass rejection rules and cause prohibited images to be accepted. S0

What should be done?

Upgrading to version 2.1.2 or later S0
Following the vendor security advisory recommendations S0, S1

Chain of evidence and sources2 verified claims

trusted-repos-policy bileşeni kayıt defteri ana bilgisayar adını büyük/küçük harf duyarlı olarak karşılaştırmaktadır.

S0 · daybreach-canonical S1 · cvelist

Büyük veya karışık harfli ana bilgisayar adları red kurallarını atlayarak kabul alabilmektedir.

S0 · daybreach-canonical S1 · cvelist

Show the technical text from the sources

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.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

CWE: CWE-178

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-63121 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

ID	VENDOR	PRODUCT	ACTION
1	kubewarden	policies	View

Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCORE	VERSION	SEVERITY	VECTOR	SOURCE
6.3	CVSS V3_1	MEDIUM	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L	CVE CNA
6.3	CVSS V31	MEDIUM	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L	NVD

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.

Restrict access to internet-facing services and apply network segmentation.

Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.

Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-63121 is associated with the following CWEs:

CWE-178: Common Weakness Enumeration Entry CWE-178

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-63121 weaknesses.

CAPEC-66: SQL Injection CAPEC-126: Path Traversal CAPEC-28: OS Command Injection

Attack Vector and Accessibility

ExposureAğ üzerinden

PermissionsGerekmiyor

UserGerekiyor

Official Sources and Advisories

https://github.com/kubewarden/policies/security/advisories/GHSA-8p62-9vh2-272pvendor-advisory https://github.com/kubewarden/policies/commit/bc5597fcbbb0bc464b714ca7ff645c9743dea41bvendor-advisory https://github.com/kubewarden/policies/tree/trusted-repos-policy/v2.1.2vendor-advisory

CVSS Vector Radar Chart

6.3 / 10

Vulnerability Scoring Details

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack VectorNetwork

Attack ComplexityLow

Privileges RequiredNone required

User Interaction—

Confidentiality (Gizlilik)Low

Integrity (Bütünlük)Low

Availability (Erişilebilirlik)Low

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

kubewarden

Weakness Type (CWE & CAPEC)

CWE-178

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

Get a free key Documentation

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-63121"