CVE-2026-122266AWS aws-network-policy-agent vulnerability
CVE-2026-122266 is a vulnerability in AWS aws-network-policy-agent, rated medium (6.3 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
The record does not classify the weakness yet; the description below says what the reporter found.
How it is reached
An attacker can exploit it from the same local network segment, with an ordinary user account, and nobody has to click anything.
What an attacker gains
The scored direct impact on the component itself is low. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.27% chance of exploitation activity in the next 30 days, higher than 20% of scored CVEs.
What to do
- Upgrade AWS aws-network-policy-agent to 1.3.7 or later. Other affected products have their own fixed versions on this page.
- Segment the networks that can reach it.
Description from NVD
Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS Network Policy Agent before 1.3.7 (VPC CNI before 1.22.3) might allow an authenticated adjacent user to bypass NetworkPolicy ingress enforcement on co-located pods via eBPF conntrack map poisoning using crafted AF_PACKET frames.
To remediate this issue, users should upgrade to Amazon VPC CNI Managed Add-on v1.22.3 or later (which includes Network Policy Agent v1.3.7).
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- AWS aws-network-policy-agent. Start from where it runs and what it is connected to.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
Questions to answer about your own systems
- Where does AWS aws-network-policy-agent run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Advisories
Releases
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.