Kyverno before 1.16.4 automatically attaches the admission controller's ServiceAccount token to outbound HTTP requests in apiCall service mode… (CVE-2026-84195)
Description
Kyverno versions prior to 1.16.4 have a vulnerability where the admission controller's ServiceAccount token is automatically attached to outbound HTTP requests in apiCall service mode without explicit authorization headers. This behavior allows attackers to exfiltrate the token by directing apiCall requests to external or attacker-controlled endpoints, potentially gaining full control over Kyverno policies and cluster resources.
CVSS v3.1
Score 7.7high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kyverno before version 1.16.4 automatically includes the admission controller's ServiceAccount token in outbound HTTP requests made in apiCall service mode without requiring explicit authorization headers. This flaw enables attackers to trick the system into sending the token to external or malicious endpoints, which can then be used to fully control Kyverno policies and manipulate cluster resources. The vulnerability is identified as CVE-2026-84195 and has a CVSS 3.1 base score of 7.7, indicating high severity. No known exploits in the wild have been reported, and no patch links or vendor advisories are provided in the input data.
Potential Impact
If exploited, attackers can exfiltrate the admission controller's ServiceAccount token, granting them full control over Kyverno policies and the ability to manipulate cluster resources. This can lead to unauthorized policy changes and potential compromise of the Kubernetes cluster environment. The vulnerability has a high severity rating with a CVSS score of 7.7, reflecting the significant confidentiality impact and the potential for privilege escalation within the cluster.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix information is provided, users should monitor vendor communications for updates. Until a fix is available, avoid exposing apiCall service mode to untrusted or external endpoints to prevent token exfiltration.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-4x34-82r8-65cf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-84195"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a96f307acd9273b49e490e9
Added to database: 09/01/2026, 15:45:11 UTC
Last enriched: 09/07/2026, 21:37:41 UTC
Last updated: 10/15/2026, 06:48:19 UTC
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.