Missing Authorization Affecting kyverno-background-controller-1.18 package, versions <1.18.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.4% (34th 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-KYVERNOBACKGROUNDCONTROLLER118-19385644
  • published28 Aug 2026
  • disclosed26 Aug 2026

Introduced: 26 Aug 2026

NewCVE-2026-54523  (opens in a new tab)
CWE-862  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kyverno-background-controller-1.18 to version 1.18.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kyverno-background-controller-1.18 package and not the kyverno-background-controller-1.18 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. From 1.18.0 until 1.18.2, the NamespacedMutatingPolicy CEL compiler exposes the generator library to matchConditions, allowing a namespace-scoped policy to invoke generator.apply(namespace, resources) with an arbitrary target namespace. The validation in pkg/cel/policies/mpol/validate.go checks that the policy compiles but does not enforce namespace scope, and GenerateResources in pkg/cel/libs/context.go does not reject the cross-namespace target. A user who can create NamespacedMutatingPolicy objects in one namespace can cause the admission controller, operating with cluster-wide privileges, to create ConfigMaps, NetworkPolicies, Secrets, RoleBindings, and other resources in another namespace, enabling unauthorized modification and potential privilege escalation. This issue is fixed in version 1.18.2.