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).
Fix
Vendor advisories in the News 1
- CVE-2026-86831: Improper validation of pod identifier uniqueness in aws-network-policy-agent in Amazon EKS AWS Security Bulletins · 2026-09-16
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-20 18:07
- First seenCVSS 8.7NVD modified 2026-10-20 19:19
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 5
- https://aws.amazon.com/security/security-bulletins/2026-113-aws/
- https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.22.4
- https://github.com/aws/amazon-vpc-cni-k8s/security/advisories/GHSA-gjc7-c7mx-x8f3
- https://github.com/aws/aws-network-policy-agent/releases/tag/v1.4.0
- https://github.com/aws/aws-network-policy-agent/security/advisories/GHSA-7xv7-8r3j-3j25