Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-122310

Kyverno 1.19.1 before 1.19.2 Privilege Escalation via Policy apiCall urlPath

Products / packages kyverno

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 06/11/2026, 02:20:32 UTC
VulnCheck · CVSS:4.0 · 9.4
Assessment vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
VulnCheck · CVSS:3.1 · 9.9
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

critical9.9

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

Kyverno 1.19.1 before 1.19.2 has a privilege escalation vulnerability via Policy apiCall urlPath, allowing a namespace-scoped user to reach cluster-scoped endpoints. The weakness is due to an interpretation conflict. A user with Policy creation access is required.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

kyverno · VulnCheck

kyverno

2 ranges
VulnCheck version evidence

Package identity

pkg:golang/github.com/kyverno/kyvernoExplore github.com/kyverno/kyverno →

Identity supplied by VulnCheck. Version matching requires compatible range evidence.

Compare with this publisher’s ranges. This does not inspect your installation.

affected

1.19.1 → before 1.19.2

semver versions

unaffected

1.19.2

semver versions

unknown

Other versions: unaffected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

Kyverno from 1.19.1 before 1.19.2 validates a Policy's context.apiCall urlPath after cleaning it but executes the raw path, whose fragment or query the Kubernetes client discards. A namespace-scoped user who can create a Policy can hide ../ segments behind # or ? to reach cluster-scoped endpoints with Kyverno's ServiceAccount, gaining cluster admin.

References

2 sources
kyverno/kyverno · security/advisories/GHSA-3xfv-vq8x-qhg4
Vendor advisoryVulnCheck
www.vulncheck.com/advisories/kyverno-1.19.1-before-1.19.2-privilege-escalation-via-policy-apicall-urlpath
Security advisoryVulnCheck

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-122310

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-436 ↗

Interpretation Conflict

VulnCheck

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

VulnCheck · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:a:kyverno:kyverno:*:*:*:*:*:*:*:*

From (inclusive): 1.19.1

Before: 1.19.2

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:a:kyverno:kyverno:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "1.19.2",
            "versionStartIncluding": "1.19.1"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
VulnCheck

Assigning organization

2026-11-05

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.