CVE-2026-86831

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

To 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).

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release.
github_release Patch Available

v1.4.0

Patch available: aws/aws-network-policy-agent v1.4.0

https://github.com/aws/aws-network-policy-agent/releases/tag/v1.4.0
github_release Patch Available

v1.22.4

Patch available: aws/amazon-vpc-cni-k8s v1.22.4

https://github.com/aws/amazon-vpc-cni-k8s/releases/tag/v1.22.4

Vendor Advisories for CVE-2026-86831(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 03:57 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 05:19 UTCEG score recompute
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 17:59 UTCEG score recompute
  6. 2026-09-16 20:59 UTCEG score recompute
  7. 2026-09-16 19:54 UTCEG score recompute
  8. 2026-09-16 19:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86831?
CVE-2026-86831 is a high vulnerability published on September 16, 2026. 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…
When was CVE-2026-86831 disclosed?
CVE-2026-86831 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86831 actively exploited?
CVE-2026-86831 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.9% of all scored CVEs.
What is the CVSS score of CVE-2026-86831?
CVE-2026-86831 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-86831?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86831, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86831

Explore →

Is Your Infrastructure Affected by CVE-2026-86831?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs