{"id":"CVE-2026-122266","kind":"vulnerability","aliases":["CVE-2026-122266"],"related":[],"title":"CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS","description":"CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS\n\n### CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS\n\nBulletin ID: 2026-170-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/04/2026 13:30 PM PST\n\nDescription:\n\nAmazon EKS Network Policy Agent (aws-network-policy-agent) is an open-source component of the Amazon VPC CNI that enforces Kubernetes NetworkPolicy on Amazon EKS clusters.\n\nWe identified CVE-2026-122266, an issue in Amazon EKS Network Policy Agent (aws-network-policy-agent). Improper isolation of shared eBPF connection tracking state might allow an authenticated adjacent user to bypass NetworkPolicy ingress enforcement on co-located pods.\n\nImpacted versions:\n\n- aws-network-policy-agent < 1.3.7\n- Amazon VPC CNI Managed Add-on < 1.22.3\n\nResolution:\n\nThis issue has been addressed in aws-network-policy-agent versions 1.3.7 and amazon-vpc-cni-k8s version 1.22.3. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.\n\nWorkarounds:\n\nThere are no workarounds available.\n\nReferences:\n\n- CVE-2026-122266\n- GHSA-mm5f-ggvx-hmvw\n\n Please email aws-security@amazon.com with any security questions or concerns.","summary":"The aws-network-policy-agent in Amazon EKS fails to isolate shared eBPF connection tracking state, so an authenticated user on an adjacent pod can bypass NetworkPolicy ingress enforcement on co-located pods. The result is that traffic a policy should block can reach pods it was meant to protect.","severity":"medium","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["aws","eks","infrastructure","kubernetes","lab-disclosure","networkpolicy"],"not_affected_if":["fixed-version","no-network-policy-enforcement"],"how_to_check":"- Check the version of aws-network-policy-agent and the Amazon VPC CNI managed add-on in the cluster.\n- Confirm whether the cluster uses Kubernetes NetworkPolicy enforced by this agent (unknown whether the sources list a specific command).","fix":"- aws-network-policy-agent: `1.3.7`\n- Amazon VPC CNI Managed Add-on: `1.22.3`\n- amazon-vpc-cni-k8s: `1.22.3`","status":"open","published_at":null,"first_seen_at":"2026-11-04T22:11:43+00:00","triaged_at":"2026-11-04T22:14:45+00:00","updated_at":"2026-11-04T22:14:45+00:00","category":"infrastructure","confidence":0.6,"triage":{"at":"2026-11-04T22:14:45Z","model":"claude-haiku-5-5","output":{"fix":"- aws-network-policy-agent: `1.3.7`\n- Amazon VPC CNI Managed Add-on: `1.22.3`\n- amazon-vpc-cni-k8s: `1.22.3`","reach":"local","title":"Amazon EKS: network policy agent flaw lets pods bypass ingress rules","impact":"medium","summary":"The aws-network-policy-agent in Amazon EKS fails to isolate shared eBPF connection tracking state, so an authenticated user on an adjacent pod can bypass NetworkPolicy ingress enforcement on co-located pods. The result is that traffic a policy should block can reach pods it was meant to protect.","audience":"businesses","category":"infrastructure","nicknames":[],"who_cares":["eks","kubernetes","aws","networkpolicy"],"confidence":0.6,"fix_status":"available","needs_auth":"yes","worst_case":"Network policy ingress rules bypassed on co-located pods","analyst_note":"","how_to_check":"- Check the version of aws-network-policy-agent and the Amazon VPC CNI managed add-on in the cluster.\n- Confirm whether the cluster uses Kubernetes NetworkPolicy enforced by this agent (unknown whether the sources list a specific command).","plain_action":"","needs_analyst":false,"not_affected_if":["fixed-version","no-network-policy-enforcement"],"who_is_affected":"Clusters on Amazon EKS that use the aws-network-policy-agent to enforce Kubernetes NetworkPolicy are exposed, and the attacker must already be an authenticated user on an adjacent pod. Teams whose clusters run an unaffected version or do not rely on this agent for policy enforcement can skip it. The sources do not say which default configurations enable the agent.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000793,"input_tokens":4636,"output_tokens":659,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-122266':3A,20A,23A,86C,103C,171C,277C '-170':121C '-2026':2A,19A,22A,85C,102C,170C,276C '1.22.3':224C,246C '1.3.7':216C,238C '11/04/2026':132C '13':133C '2026':120C '30':134C 'add':222C 'add-on':221C 'address':230C 'adjac':55B,197C 'agent':14A,37B,97C,114C,142C,147C,179C,184C,215C,236C 'allow':194C 'amazon':16A,39B,99C,116C,138C,156C,164C,175C,217C,241C 'amazon-vpc-cni-k8s':240C 'attent':129C 'authent':51B,196C 'avail':273C 'aw':11A,24B,34B,94C,111C,122C,124C,144C,181C,212C,233C 'aws-network-policy-ag':10A,33B,93C,110C,143C,180C,211C,232C 'aws-security@amazon.com':285C 'block':75B 'bulletin':118C 'bypass':58B,200C 'cluster':166C 'cni':158C,219C,243C 'co':64B,206C 'co-loc':63B,205C 'code':260C 'compon':153C 'concern':291C 'connect':46B,190C 'content':125C 'cve':1A,18A,21A,84C,101C,169C,275C 'date':131C 'deriv':259C 'descript':137C 'disclosur':30B 'ebpf':45B,189C 'ek':17A,25B,40B,100C,117C,139C,165C,176C 'email':284C 'enforc':61B,160C,203C 'ensur':255C 'fail':41B 'fix':267C 'fork':257C 'ggvx':281C 'ghsa':279C 'ghsa-mm5f-ggvx-hmvw':278C 'hmvw':282C 'id':119C 'identifi':168C 'impact':209C 'import':127C 'improp':4A,87C,104C,185C 'incorpor':264C 'infrastructur':26B 'ingress':60B,202C 'isol':5A,43B,88C,105C,186C 'issu':173C,227C 'k8s':244C 'kubernet':27B,161C 'lab':29B 'lab-disclosur':28B 'latest':252C 'locat':65B,207C 'manag':220C 'meant':81B 'might':193C 'mm5f':280C 'network':12A,35B,95C,112C,140C,145C,177C,182C,213C,234C 'networkpolici':31B,59B,162C,201C 'new':266C 'open':151C 'open-sourc':150C 'patch':262C 'pleas':283C 'pm':135C 'pod':56B,66B,78B,208C 'polici':13A,36B,73B,96C,113C,141C,146C,178C,183C,214C,235C 'protect':83B 'pst':136C 'public':130C 'question':289C 'reach':77B 'recommend':248C 'refer':274C 'requir':128C 'resolut':225C 'resourc':8A,91C,108C 'result':68B 'scope':123C 'secur':288C 'share':7A,44B,90C,107C,188C 'sourc':152C 'state':48B,192C 'track':47B,191C 'traffic':71B 'type':126C 'upgrad':249C 'user':52B,198C 'version':210C,237C,245C,253C 'vpc':157C,218C,242C 'workaround':268C,272C","nicknames":[],"mitigations":[],"who_affected":"Clusters on Amazon EKS that use the aws-network-policy-agent to enforce Kubernetes NetworkPolicy are exposed, and the attacker must already be an authenticated user on an adjacent pod. Teams whose clusters run an unaffected version or do not rely on this agent for policy enforcement can skip it. The sources do not say which default configurations enable the agent.","tier":"C","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"businesses","plain_action":null,"pkeys":[],"ptokens":[],"labels":["aws","eks","infrastructure","kubernetes","labdisclosure","medium","networkpolicy"],"campaign_type":null,"first_public_at":null,"kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/rss/2026-170-aws/#CVE-2026-122266","url":"https://aws.amazon.com/security/security-bulletins/rss/2026-170-aws/","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-11-04T22:11:43+00:00","fetched_at":"2026-11-04T22:11:43+00:00","note":"AWS: CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS"}],"documents":[{"id":70913,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-170-aws/","title":"AWS: CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS","kind":"advisory","source":"lab","publisher":"research","text":"CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS\n\n### CVE-2026-122266 - Improper isolation of shared resources in aws-network-policy-agent in Amazon EKS\n\nBulletin ID: 2026-170-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/04/2026 13:30 PM PST\n\nDescription:\n\nAmazon EKS Network Policy Agent (aws-network-policy-agent) is an open-source component of the Amazon VPC CNI that enforces Kubernetes NetworkPolicy on Amazon EKS clusters.\n\nWe identified CVE-2026-122266, an issue in Amazon EKS Network Policy Agent (aws-network-policy-agent). Improper isolation of shared eBPF connection tracking state might allow an authenticated adjacent user to bypass NetworkPolicy ingress enforcement on co-located pods.\n\nImpacted versions:\n\n- aws-network-policy-agent < 1.3.7\n- Amazon VPC CNI Managed Add-on < 1.22.3\n\nResolution:\n\nThis issue has been addressed in aws-network-policy-agent versions 1.3.7 and amazon-vpc-cni-k8s version 1.22.3. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.\n\nWorkarounds:\n\nThere are no workarounds available.\n\nReferences:\n\n- CVE-2026-122266\n- GHSA-mm5f-ggvx-hmvw\n\n Please email aws-security@amazon.com with any security questions or concerns.","published_at":null,"relation":"advisory","confidence":null,"note":null}],"exploit_sources":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}