CVE-2026-122302

validatingZero is analyzing and reversing it now.

GHSA-p456-76q8-jj5q ↗EUVD-2026-117213 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
kyverno main @ 21168fdf
fixed in v1.19.2
CWE-269 Improper Privilege Management
ETK-2026-3570Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/kyverno/kyverno
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Kyverno versions before 1.19.2 incorrectly authorize generate rules using controller privileges instead of the policy author's permissions. A namespace administrator able to create a namespaced Policy may cause resources to be created or cloned beyond their assigned RBAC scope, including in other namespaces or at cluster scope.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Kyverno to version 1.19.2 or later. Until upgraded, restrict creation and modification of Policies containing generate rules to tightly trusted administrators.

fixed in v1.19.2

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 02:25Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-05 02:25Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-122302

{
  "etk_id": "ETK-2026-3570",
  "cve_id": "CVE-2026-122302",
  "display_id": "CVE-2026-122302",
  "ghsa_id": "GHSA-p456-76q8-jj5q",
  "euvd_id": "EUVD-2026-117213",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Kyverno generate-rule authorization privilege escalation",
  "summary": "Kyverno versions before 1.19.2 incorrectly authorize generate rules using controller privileges instead of the policy author's permissions. A namespace administrator able to create a namespaced Policy may cause resources to be created or cloned beyond their assigned RBAC scope, including in other namespaces or at cluster scope.",
  "mitigation": "Upgrade Kyverno to version 1.19.2 or later. Until upgraded, restrict creation and modification of Policies containing generate rules to tightly trusted administrators.",
  "vendor": "kyverno",
  "product": "kyverno",
  "affected": [
    {
      "affected_notes": [
        "main @ 21168fdf"
      ],
      "affected_ranges": [],
      "ecosystem": "go",
      "fixed_versions": [
        "v1.19.2"
      ],
      "package_name": "github.com/kyverno/kyverno",
      "purl": "pkg:golang/github.com/kyverno/kyverno"
    }
  ],
  "cwes": [
    269
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 39.322937683333336,
  "t0_at": "2026-11-05T02:25:07.653000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T02:25:07.653000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T02:25:07.653000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-122302"
    }
  }
}

published 2026-11-05 02:45Z
last change 2026-11-05 03:57Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.