Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.9
Docker hardened reports‑server images allow Kyverno cross‑namespace access
published 10 days ago
Summary
Versions of Kyverno older than 1.16.3 (or 1.15.3) that are bundled in the listed Docker hardened reports‑server images let any user who can create a namespaced policy make Kyverno’s admission controller run Kubernetes API calls with its own privileges across the whole cluster. This can expose configuration data and permit unwanted changes outside the intended namespace. Upgrade the Kyverno component in those images to version 1.16.3 or later and limit who can create policies to mitigate the risk.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Alpine:3.24 | docker hardened images | reports-server-dev | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | reports-server-fips-dev | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | reports-server-fips | All versions |
| Docker Hardened Images:Alpine:3.24 | docker hardened images | reports-server | All versions |
Original advisory text
Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1.16.3 and 1.15.3…
Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1.16.3 and 1.15.3 have a critical authorization boundary bypass in namespaced Kyverno Policy apiCall. The resolved `urlPath` is executed using the Kyverno admission controller ServiceAccount, with no enforcement that the request is limited to the policy’s namespace. As a result, any authenticated user with permission to create a namespaced Policy can cause Kyverno to perform Kubernetes API requests using Kyverno’s admission controller identity, targeting any API path allowed by that ServiceAccount’s RBAC. This breaks namespace isolation by enabling cross-namespace reads (for example, ConfigMaps and, where permitted, Secrets) and allows cluster-scoped or cross-namespace writes (for example, creating ClusterPolicies) by controlling the urlPath through context variable substitution. Versions 1.16.3 and 1.15.3 contain a patch for the vulnerability.
References
- https://scout.docker.com/v/DHI-xxq5-ochf-d5vc-6vzk Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-22039 Vendor Advisory
- https://github.com/kyverno/kyverno/security/advisories/GHSA-8p9x-46gm-qfx2 Vendor Advisory
- https://github.com/kyverno/kyverno/commit/eba60fa856c781bcb9c3be066061a3df03ae4e... Patch
- https://github.com/kyverno/kyverno/commit/e0ba4de4f1e0ca325066d5095db51aec45b140... Patch
- https://github.com/advisories/GHSA-8p9x-46gm-qfx2 Vendor Advisory
- https://pkg.go.dev/vuln/GO-2026-4381 Vendor Advisory
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker full control (estimated)
Timeline
Published11 Nov 2026
Updated16 Nov 2026
First seen16 Nov 2026
Sources
DHI-xxq5-ochf-d5vc-6vzk · OSV
Track software like this
Free during beta