Incorrect Authorization Affecting kyverno-notation-aws package, versions <1.1-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.27% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-KYVERNONOTATIONAWS-18341337
  • published28 Jul 2026
  • disclosed24 Apr 2026

Introduced: 24 Apr 2026

CVE-2026-41068  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kyverno-notation-aws to version 1.1-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kyverno-notation-aws package and not the kyverno-notation-aws package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Kyverno is a policy engine designed for cloud native platform engineering teams. The patch for CVE-2026-22039 fixed cross-namespace privilege escalation in Kyverno's apiCall context by validating the URLPath field. However, the ConfigMap context loader has the identical vulnerability — the configMap.namespace field accepts any namespace with zero validation, allowing a namespace admin to read ConfigMaps from any namespace using Kyverno's privileged service account. This is a complete RBAC bypass in multi-tenant Kubernetes clusters. An updated fix is available in version 1.17.2.