{"id":"GHSA-mm5f-ggvx-hmvw","kind":"vulnerability","aliases":["GHSA-mm5f-ggvx-hmvw"],"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 component of Amazon EKS, which enforces Kubernetes NetworkPolicy, has improper isolation of shared eBPF connection tracking state. An authenticated user on an adjacent pod can bypass NetworkPolicy ingress enforcement on co-located pods.","severity":"medium","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["aws","eks","infrastructure","kubernetes","lab-disclosure","network-policy","vpc-cni"],"not_affected_if":["fixed-version","no-network-policy"],"how_to_check":"- Check the version of aws-network-policy-agent running in the cluster and compare it with `1.3.7`.\n- Check the Amazon VPC CNI Managed Add-on version and compare it with `1.22.3`.\n- Check whether the cluster uses forked or derivative code of the network policy agent.","fix":"- aws-network-policy-agent: move to `1.3.7` or later.\n- Amazon VPC CNI Managed Add-on: move to `1.22.3` or later.","status":"open","published_at":null,"first_seen_at":"2026-11-04T22:11:43+00:00","triaged_at":"2026-11-04T22:14:46+00:00","updated_at":"2026-11-04T22:14:46+00:00","category":"infrastructure","confidence":0.8,"triage":{"at":"2026-11-04T22:14:46Z","model":"claude-haiku-5-5","output":{"fix":"- aws-network-policy-agent: move to `1.3.7` or later.\n- Amazon VPC CNI Managed Add-on: move to `1.22.3` or later.","reach":"local","title":"Amazon EKS network policy agent lets pods bypass ingress NetworkPolicy enforcement","impact":"medium","summary":"The aws-network-policy-agent component of Amazon EKS, which enforces Kubernetes NetworkPolicy, has improper isolation of shared eBPF connection tracking state. An authenticated user on an adjacent pod can bypass NetworkPolicy ingress enforcement on co-located pods.","audience":"businesses","category":"infrastructure","nicknames":[],"who_cares":["eks","kubernetes","aws","vpc-cni","network-policy"],"confidence":0.8,"fix_status":"available","needs_auth":"yes","worst_case":"Pods on the same node bypass ingress network policy restrictions.","analyst_note":"","how_to_check":"- Check the version of aws-network-policy-agent running in the cluster and compare it with `1.3.7`.\n- Check the Amazon VPC CNI Managed Add-on version and compare it with `1.22.3`.\n- Check whether the cluster uses forked or derivative code of the network policy agent.","plain_action":"","needs_analyst":false,"not_affected_if":["fixed-version","no-network-policy"],"who_is_affected":"Teams running Amazon EKS clusters that use the VPC CNI network policy agent to enforce Kubernetes NetworkPolicy, where authenticated workloads share nodes with the pods being protected. Clusters on versions at or above the fixed releases, or without NetworkPolicy enforcement, are not affected. The sources do not say whether managed-only setups differ from self-managed forks beyond the advice to patch derivative code.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"medium"},"cost_usd":0.000803,"input_tokens":4656,"output_tokens":675,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-122266':3A,83C,100C,168C,274C '-170':118C '-2026':2A,82C,99C,167C,273C '1.22.3':221C,243C '1.3.7':213C,235C '11/04/2026':129C '13':130C '2026':117C '30':131C 'add':219C 'add-on':218C 'address':227C 'adjac':69B,194C 'agent':14A,46B,94C,111C,139C,144C,176C,181C,212C,233C 'allow':191C 'amazon':16A,49B,96C,113C,135C,153C,161C,172C,214C,238C 'amazon-vpc-cni-k8s':237C 'attent':126C 'authent':65B,193C 'avail':270C 'aw':11A,28B,43B,91C,108C,119C,121C,141C,178C,209C,230C 'aws-network-policy-ag':10A,42B,90C,107C,140C,177C,208C,229C 'aws-security@amazon.com':282C 'bulletin':115C 'bypass':72B,197C 'cluster':163C 'cni':40B,155C,216C,240C 'co':78B,203C 'co-loc':77B,202C 'code':257C 'compon':47B,150C 'concern':288C 'connect':61B,187C 'content':122C 'cve':1A,81C,98C,166C,272C 'date':128C 'deriv':256C 'descript':134C 'disclosur':34B 'ebpf':60B,186C 'ek':17A,29B,50B,97C,114C,136C,162C,173C 'email':281C 'enforc':52B,75B,157C,200C 'ensur':252C 'fix':264C 'fork':254C 'ggvx':21A,26A,278C 'ghsa':19A,24A,276C 'ghsa-mm5f-ggvx-hmvw':18A,23A,275C 'hmvw':22A,27A,279C 'id':116C 'identifi':165C 'impact':206C 'import':124C 'improp':4A,56B,84C,101C,182C 'incorpor':261C 'infrastructur':30B 'ingress':74B,199C 'isol':5A,57B,85C,102C,183C 'issu':170C,224C 'k8s':241C 'kubernet':31B,53B,158C 'lab':33B 'lab-disclosur':32B 'latest':249C 'locat':79B,204C 'manag':217C 'might':190C 'mm5f':20A,25A,277C 'network':12A,36B,44B,92C,109C,137C,142C,174C,179C,210C,231C 'network-polici':35B 'networkpolici':54B,73B,159C,198C 'new':263C 'open':148C 'open-sourc':147C 'patch':259C 'pleas':280C 'pm':132C 'pod':70B,80B,205C 'polici':13A,37B,45B,93C,110C,138C,143C,175C,180C,211C,232C 'pst':133C 'public':127C 'question':286C 'recommend':245C 'refer':271C 'requir':125C 'resolut':222C 'resourc':8A,88C,105C 'scope':120C 'secur':285C 'share':7A,59B,87C,104C,185C 'sourc':149C 'state':63B,189C 'track':62B,188C 'type':123C 'upgrad':246C 'user':66B,195C 'version':207C,234C,242C,250C 'vpc':39B,154C,215C,239C 'vpc-cni':38B 'workaround':265C,269C","nicknames":[],"mitigations":[],"who_affected":"Teams running Amazon EKS clusters that use the VPC CNI network policy agent to enforce Kubernetes NetworkPolicy, where authenticated workloads share nodes with the pods being protected. Clusters on versions at or above the fixed releases, or without NetworkPolicy enforcement, are not affected. The sources do not say whether managed-only setups differ from self-managed forks beyond the advice to patch derivative code.","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","vpccni"],"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/#GHSA-mm5f-ggvx-hmvw","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"}