Quick answers
- Is CVE-2026-122266 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-122266 being exploited in the wild.
- How severe is CVE-2026-122266?
- High severity, with a CVSS score of 8.7, published 4 November 2026.
- Which products and versions are affected?
- Amazon VPC CNI Managed Add-on < 1.22.3; Amazon Aws-Network-Policy-Agent < 1.3.7.
- Is there a fix for CVE-2026-122266?
- Yes: fixed in aws-network-policy-agent 1.3.7, Amazon VPC CNI Managed Add-on 1.22.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-122266 attacked?
- It is attacked from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-122266?
- Check whether you run Amazon VPC CNI Managed Add-on, Amazon AWS or Amazon Aws-Network-Policy-Agent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: aws-network-policy-agent 1.3.7, Amazon VPC CNI Managed Add-on 1.22.3
Technical details
The vulnerability stems from improper isolation of shared eBPF connection tracking state within aws-network-policy-agent. An authenticated adjacent user can exploit this to bypass NetworkPolicy ingress enforcement on co-located pods. The issue affects versions prior to 1.3.7 and can be resolved by upgrading to the patched versions.
Affected products
- Amazon aws-network-policy-agent < 1.3.7
- Amazon Amazon VPC CNI Managed Add-on < 1.22.3
Timeline
- 2026-11-04: disclosed