CVE-2026-5059

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-11. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

aws-mcp-server AWS CLI Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of aws-mcp-server. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of the allowed commands list. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the MCP server. Was ZDI-CAN-27969.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation2.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
2.3%
EPSS %ILE
83rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 11, 2026

Last Modified

April 13, 2026

Advisory Details (1)

Auto-updated Oct 9, 2026
No fix on record yet.
Web page

ZDI-26-245 - TrendAI™ Zero Day Initiative™ (ZDI)

https://www.zerodayinitiative.com/advisories/ZDI-26-245/

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipaws-mcp—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
aws-mcp1.5.4, 1.5.5, 1.5.6, 1.6.0, 1.7.0
  • every version through 1.7.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 251 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 151 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 17:17 UTCEG score recompute
  2. 2026-10-15 17:17 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-15 16:32 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  4. 2026-10-14 16:33 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  5. 2026-10-14 11:17 UTCEG score recompute
  6. 2026-10-14 11:16 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.3% · 83rd percentile
  8. 2026-10-13 09:16 UTCEG score recompute
  9. 2026-10-13 09:15 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-12 16:34 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  11. 2026-10-12 15:59 UTCEG score recompute
  12. 2026-10-12 07:15 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 19:42 UTCEG score recompute
  14. 2026-10-11 16:57 UTCEG score recompute
  15. 2026-10-11 14:20 UTCEG score recompute
  16. 2026-10-11 13:49 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  19. 2026-10-08 17:13 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  4. 2026-09-24 14:04 UTCEPSS rescoreEPSS 2.3% · 82nd percentile
  5. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  6. 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  8. 2026-09-17 19:31 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  9. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  10. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  11. 2026-09-15 03:11 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  12. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  13. 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  14. 2026-09-10 09:35 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  15. 2026-09-08 22:01 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  17. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  18. 2026-09-04 05:07 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  19. 2026-09-02 14:12 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  20. 2026-09-01 13:54 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  21. 2026-09-01 04:40 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  22. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  23. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  24. 2026-08-28 21:42 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  25. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  26. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  27. 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  28. 2026-08-23 00:19 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  29. 2026-08-21 23:49 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  30. 2026-08-20 22:55 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  31. 2026-08-19 17:04 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  32. 2026-08-18 13:48 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  33. 2026-08-17 13:47 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  34. 2026-08-16 14:56 UTCEPSS rescoreEPSS 1.9% · 78th percentile
  35. 2026-08-16 11:08 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-08-16 06:59 UTCEG score recompute
  37. 2026-08-16 06:59 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-08-15 01:30 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  39. 2026-08-14 22:28 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-08-14 18:19 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-08-14 13:18 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-08-14 09:09 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-08-14 05:00 UTCEG score recompute
  44. 2026-08-14 05:00 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-08-13 22:00 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  46. 2026-08-13 09:18 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-08-13 03:30 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-08-12 23:21 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-08-12 19:13 UTCEG score recompute
  50. 2026-08-12 19:13 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-12 13:51 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  52. 2026-08-11 23:31 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-08-11 19:22 UTCEG score recompute
  54. 2026-08-11 19:22 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-08-11 07:05 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-11 02:54 UTCEG score recompute
  57. 2026-08-11 02:54 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-08-11 00:00 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  59. 2026-08-10 09:32 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-08-10 05:23 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-08-10 01:15 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-08-09 21:05 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-09 16:57 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-09 12:48 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-09 08:34 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-08-09 04:25 UTCEG score recompute
  67. 2026-08-09 04:25 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-08 16:37 UTCEPSS rescoreEPSS 1.9% · 77th percentile
  69. 2026-08-08 11:22 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-08-08 06:46 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-08 02:37 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-08-07 22:28 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-08-07 18:19 UTCEG score recompute
  74. 2026-08-07 18:19 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-08-07 14:11 UTCGHSA enrichmentGHSA-fgmx-xfp3-w28p · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5059?
CVE-2026-5059 is a critical-severity vulnerability; its CVE record was published on April 11, 2026. aws-mcp-server AWS CLI Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of aws-mcp-server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling…
When was CVE-2026-5059 made public?
CVE-2026-5059 was made public on March 30, 2026: that is the date its CVE record's CNA, Zero Day Initiative, gives for when the vulnerability was made public. The CVE record itself was published on April 11, 2026. EchelonGraph's copy of the record carries a last-modified date of April 13, 2026; the record at its source may have been updated since.
Is CVE-2026-5059 actively exploited?
CVE-2026-5059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-5059?
CVE-2026-5059 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-5059?
No fix for CVE-2026-5059 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5059

Explore →

Is Your Infrastructure Affected by CVE-2026-5059?

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

Book a Demo →Browse All CVEs