CVE-2026-86831: Improper validation of pod identifier uniqueness in aws-network-policy-agent in Amazon EKS
Improper validation of pod identifier uniqueness in aws-network-policy-agent in Amazon EKS Network Policy Agent before v1.4.0 might allow an authenticated remote user to bypass NetworkPolicy enforcement on co-located pods in other namespaces via crafted pod and namespace names that produce pod identifier collisions.
To remediate this issue, users should upgrade to Amazon EKS Network Policy Agent 1.4.0 or later and Amazon VPC CNI Managed Add-on v1.22.4 or later (which includes Network Policy Agent v1.4.0).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
aws-network-policy-agentto a version that resolves this vulnerability.Fixed in 1.4.0 - Upgrade
Upgrade
Amazon VPC CNI Managed Add-onto a version that resolves this vulnerability.Fixed in v1.22.4
Event History
Frequently Asked Questions
Which environments are exposed to this issue?
Amazon EKS environments using Network Policy Agent versions before 1.4.0 are affected. Exploitation applies to co-located pods in different namespaces where crafted pod and namespace names can create identifier collisions.
What level of access does an attacker need?
An attacker must be an authenticated remote user and have the ability to use crafted pod and namespace names that produce a pod identifier collision. No user interaction is required.
What is the impact of a successful exploit?
A successful exploit can bypass NetworkPolicy enforcement for co-located pods in other namespaces. The reported impact includes high confidentiality and integrity effects, with no availability impact.
What should be upgraded to remediate the issue?
Upgrade Amazon EKS Network Policy Agent to version 1.4.0 or later. For the Amazon VPC CNI Managed Add-on, upgrade to version 1.22.4 or later, which includes Network Policy Agent 1.4.0.