AWS aws-network-policy-agent
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.4.0
Fixed in 1.4.0
- >= 1.14.0, < 1.22.4
Fixed in 1.22.4
Mitigation
Upgrade aws-network-policy-agent to 1.4.0 or later.
Upgrade amazon-vpc-cni-k8s to 1.22.4 or later.
References
- Patch github.com/aws/amazon-vpc-cni-k8s/releases/tag…
- Patch github.com/aws/aws-network-policy-agent/releas…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-11…
2 more
- Vendor advisory github.com/aws/aws-network-policy-agent/securi…
- Vendor advisory github.com/aws/amazon-vpc-cni-k8s/security/adv…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.