{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-86831 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86831 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-86831 is a high-severity vulnerability in AWS amazon-vpc-cni-k8s, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-86831 and fix it if it is affected.\n\nWhat it is: CVE-2026-86831 is a high-severity vulnerability in AWS amazon-vpc-cni-k8s, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-86831 in the wild and no public exploit code.\n\nAffected product: AWS amazon-vpc-cni-k8s. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-86831/ (Markdown: https://insights.sbomify.com/CVE-2026-86831/index.md)","id":"CVE-2026-86831","markdown":"https://insights.sbomify.com/CVE-2026-86831/index.md","name":"CVE-2026-86831","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EKS Network Policy Agent","requires_auth":"high_privilege","summary":"Authenticated users can bypass NetworkPolicy enforcement on co-located pods in other namespaces by exploiting pod identifier collisions in the AWS Network Policy Agent.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1289","name":"Improper Validation of Unsafe Equivalence in Input"}],"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.\n\nTo 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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper validation of pod identifier uniqueness in aws-network-policy-agent in Amazon EKS","id":"CVE-2026-86831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"MetForm \u003c 4.3.1 - Unauthenticated Form Entry Data Disclosure via REST API","id":"CVE-2026-86832"},"packages":[],"prev":{"headline":"Incorrect privilege assignment in Temporary Elevated Access Management (TEAM) for AWS IAM Identity Center","id":"CVE-2026-86830"},"products":["amazon-vpc-cni-k8s","aws-network-policy-agent"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["AWS"]},"summary":"Authenticated users can bypass NetworkPolicy enforcement on co-located pods in other namespaces by exploiting pod identifier collisions in the AWS Network Policy Agent.","url":"https://insights.sbomify.com/CVE-2026-86831/"}