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).
No summary for this CVE yet.
CVSS Vector Breakdown
Exploitability
AV:NAttack VectorNetwork
AC:LAttack ComplexityLow
PR:HPrivileges RequiredHigh
UI:NUser InteractionNone
Scope
S:CScopeChanged
Impact
C:HConfidentialityHigh
I:HIntegrityHigh
A:NAvailabilityNone
Weaknesses
Affected Products
Exploitability
No known exploits, KEV entries, or remediation guidance available for this vulnerability yet.
References
https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.22.4
github.com
https://github.com/aws/amazon-vpc-cni-k8s/security/advisories/GHSA-gjc7-c7mx-x8f3
github.com
https://github.com/aws/aws-network-policy-agent/releases/tag/v1.4.0
github.com
and 2 more references View all →
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2026-86831 and every CVE in our database. Create a free account — no credit card required.
Create Free AccountPlain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows