CVE-2026-122311

waiting for further signalsZero needs more public information before it can validate it.

GHSA-p59g-p6q6-8969 ↗EUVD-2026-117222 ↗

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 >= 1.16.0, < 1.19.2
fixed in 1.19.2
ETK-2026-3576Zero's internal tracking ID, independent of the CVE number., permanent identifier
18h 36msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h45m
0
+4h
+6h
+8h
+10h
+12h

description

Kyverno 1.16.0 through 1.19.1 does not adequately constrain paths supplied to CEL resource access functions. An actor who can create a NamespacedValidatingPolicy may access or modify cluster resources beyond its namespace using the admission controller service account.

mitigation

Upgrade Kyverno to version 1.19.2 or later. Until upgraded, restrict creation of NamespacedValidatingPolicy resources to trusted administrators.

fixed in 1.19.2

check
no
exploit
no
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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
17m
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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3576",
  "cve_id": "CVE-2026-122311",
  "display_id": "CVE-2026-122311",
  "ghsa_id": "GHSA-p59g-p6q6-8969",
  "euvd_id": "EUVD-2026-117222",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Kyverno CEL resource functions",
  "summary": "Kyverno 1.16.0 through 1.19.1 does not adequately constrain paths supplied to CEL resource access functions. An actor who can create a NamespacedValidatingPolicy may access or modify cluster resources beyond its namespace using the admission controller service account.",
  "mitigation": "Upgrade Kyverno to version 1.19.2 or later. Until upgraded, restrict creation of NamespacedValidatingPolicy resources to trusted administrators.",
  "vendor": "kyverno",
  "product": "kyverno",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.16.0, < 1.19.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.19.2"
      ],
      "package_name": "kyverno",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.27992305,
  "t0_at": "2026-11-05T02:25:13.645000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T02:25:13.645000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T02:25:13.645000+00:00",
      "url": "https://github.com/advisories/GHSA-p59g-p6q6-8969"
    }
  }
}

published 2026-11-05 03:52Z
last change 2026-11-05 09:29Z

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.