Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Kyverno's PolicyException objects can be created in any namespace by default

CVSS 4.0 8.7 HIGHEUVD CVSS 4.0 8.7 CVSS 4.0 · [email protected] · Secondary 8.7 HIGHCVSS 3.1 · [email protected] · Primary 2.7 LOWCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/kyverno/kyverno 1.13.0osv · severity unknownFixed by github.com/kyverno/kyverno 1.13.0KEV status unknown

cve-program · CVE-2024-48921

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-3117

Published

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.

Read the publisher's advisory

nvd · CVE-2024-48921

Published

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.

Read the publisher's advisory

osv · GHSA-qjvc-p88j-j9rm

Published

### Summary A kyverno ClusterPolicy, ie. "disallow-privileged-containers," can be overridden by the creation of a PolicyException in a random namespace. ### Details 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. ### PoC 1. Administrator creates "disallow-privileged-containers" ClusterPolicy that applies to resources in the namespace "ubuntu-restricted" 2. Cluster user creates a PolicyException object for "disallow-privileged-containers" in namespace "ubuntu-restricted" 3. Cluster user creates a pod with a privileged container in "ubuntu-restricted" 4. Cluster user escalates to root on the node from the privileged container ### Impact Administrators attempting to enforce cluster security through kyverno policies, but that allow less privileged users to create resources

Read the publisher's advisory

osv · GO-2024-3230

Published

Kyverno's PolicyException objects can be created in any namespace by default in github.com/kyverno/kyverno

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-48921

Published

Kyverno's PolicyException objects can be created in any namespace by default

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.

Source published
29 Oct 2024 14:14:36 UTC
Source modified
29 Oct 2024 14:58:36 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · 8.7 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

euvd · EUVD-2024-3117

Published

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 a…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 29, 2024, 2:14:36 PM

dateUpdated: Oct 29, 2024, 2:58:36 PM

3 related source bulletins · separate from aliases

openSUSE-SU-2024:14447-1: govulncheck-vulndb-0.0.20241030T212825-1.1 on GA media

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

openSUSE-SU-2024:0350-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-0132 · CVE-2024-0133 · CVE-2024-10005 · CVE-2024-10006 · CVE-2024-10086 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-10452 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-39720 · CVE-2024-46872 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47401 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50052 · CVE-2024-50312 · CVE-2024-50354 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8185 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

SUSE-SU-2024:3911-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

Source published
Oct 29, 2024, 2:14:36 PM (timezone not stated)
Source modified
Oct 29, 2024, 2:58:36 PM (timezone not stated)
Saved here
15 Nov 2026 03:36:50 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 4.0 · 8.7 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

nvd · CVE-2024-48921

Published

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 a…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-285 · CWE-863

Original publisher date fields

published: 2024-10-29T15:15:10.593

lastModified: 2026-06-17T07:59:03.620

1 source CPE criteria · context only
  • cpe:2.3:a:nirmata:kyverno:*:*:*:*:*:go:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
29 Oct 2024 15:15:10 UTC
Source modified
17 Jun 2026 07:59:03 UTC
Saved here
25 Oct 2026 00:17:35 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · [email protected] · Secondary · 8.7 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

CVSS 3.1 · [email protected] · Primary · 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

osv · GHSA-qjvc-p88j-j9rm

Published

Kyverno's PolicyException objects can be created in any namespace by default

### Summary A kyverno ClusterPolicy, ie. "disallow-privileged-containers," can be overridden by the creation of a PolicyException in a random namespace. ### Details 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. ### PoC 1. Administrator creates "disallow-privileged-containers" ClusterPolicy that applies to resources in the namespace "ubuntu-restricted" 2. Cluster user creates a PolicyException object for "disallow-privileged-containers" in namespace "ubuntu-restricted" 3. Cluster user creates a pod with a privileged container in "ubuntu-restricted" 4. Cluster user escalates to root on the node from the privileged container ### Impact Administrators attempting to enforce cluster security through kyverno policies, but that allow less privileged users to create resources

Source published
29 Oct 2024 14:44:36 UTC
Source modified
10 Sep 2026 03:50:20 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS_V4 · 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

Publisher rating · HIGH

osv · GO-2024-3230

Published

Kyverno's PolicyException objects can be created in any namespace by default in github.com/kyverno/kyverno

Kyverno's PolicyException objects can be created in any namespace by default in github.com/kyverno/kyverno

Source published
30 Oct 2024 21:22:08 UTC
Source modified
4 Feb 2026 04:39:47 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 12:50 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current