Description
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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| AWS | aws-network-policy-agent | < 1.4.0 | 1.4.0 |
| AWS | amazon-vpc-cni-k8s | 1.14.0 – < 1.22.4 | 1.22.4 |
References
- https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.22.4 patch release-notes
- https://github.com/aws/aws-network-policy-agent/releases/tag/v1.4.0 patch release-notes
- https://aws.amazon.com/security/security-bulletins/2026-113-aws/ vendor-advisory
- https://github.com/aws/aws-network-policy-agent/security/advisories/GHSA-7xv7-8r3j-3j25 release-notes
- https://github.com/aws/amazon-vpc-cni-k8s/security/advisories/GHSA-gjc7-c7mx-x8f3 release-notes