How broadly exploitable is this vulnerability?

Exploitability depends on who can influence Kyverno policies and outbound connectivity. If an attacker can create or modify ClusterPolicies that use apiCall, or introduce policies referencing attacker-controlled URLs, and the admission controller can reach those URLs, the vulnerability becomes directly exploitable.

What level of access does an attacker need to take advantage of this flaw?

An attacker typically needs the ability to define or alter Kyverno policies, or to inject configurations that Kyverno loads, combined with network reachability from the admission controller to their server. Once a token is exfiltrated, the attacker's effective access may escalate to whatever permissions the admission controller's ServiceAccount holds.

What is the safest general fix pattern for this type of issue?

The safest pattern is to prevent high-privilege tokens from being automatically attached to user-influenced or policy-driven HTTP requests, and to restrict apiCall destinations to explicitly trusted, internal endpoints. Separating identities for external integrations and limiting their permissions ensures that even if a token is exposed, its blast radius remains small.

Severity:

HIGH RISK

(8.1)

Unvalidated Server-Side Request with Token Leakage (CWE-918, CWE-200) in Kyverno apiCall

CVE-2026-41323

Published:

Apr 23, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Server-Side Request Forgery and Sensitive Token Exposure

CWE:

CWE-200;CWE-918

Impact:

Cluster Compromise via Token Theft and Misused Outbound Requests

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery and Sensitive Token Exposure

CWE:

CWE-200;CWE-918

Impact:

Cluster Compromise via Token Theft and Misused Outbound Requests

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Unvalidated Server-Side Request with Token Leakage (CWE-918, CWE-200) in Kyverno apiCall

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare