CVE-2026-90617

HIGHPre-NVD 7.37.3
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 7.3Exploit: Elevated riskExposed: 0

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

A vulnerability was detected in GH05TCREW PentestAgent up to cf882dabea3ed91cef016cdd115e5426315665a2. This vulnerability affects the function run_task of the file interface/main.py of the component MCP HTTP Server. Performing a manipulation results in os command injection. The attack is possible to be carried out remotely. The exploit is now public and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The pull request to fix this issue awaits acceptance.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
64(Attend)
EG Risk 64/100SSVC: Attend

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
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
2%
EPSS %ILE
75%
KEV
Not listed

Published

September 14, 2026

Last Modified

September 15, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. No patch confirmed yet. Sources: github_pr.
generic

GitHub - GH05TCREW/pentestagent: PentestAgent is an AI agent framework for black-box security testing, supporting bug bounty, red-team, and penetration testing workflows. · GitHub

https://github.com/GH05TCREW/pentestagent/
github_pr

Require auth on MCP HTTP server + bind localhost by default (issue #90)

Upstream fix in progress (PR #101 · GH05TCREW/pentestagent, state=open)

https://github.com/GH05TCREW/pentestagent/pull/101
generic🟡 PoC Available

PentestAgent — Unauthenticated MCP HTTP Server Exposes Full Agent Control · Issue #90 · GH05TCREW/pentestagent · GitHub

https://github.com/GH05TCREW/pentestagent/issues/90

Vendor Advisories for CVE-2026-90617(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 36× 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-21 11:36 UTCGHSA enrichment
  2. 2026-09-20 23:13 UTCGHSA enrichment
  3. 2026-09-20 10:35 UTCGHSA enrichment
  4. 2026-09-19 22:07 UTCEG score recompute
  5. 2026-09-19 22:07 UTCGHSA enrichment
  6. 2026-09-19 09:43 UTCGHSA enrichment
  7. 2026-09-18 21:16 UTCEG score recompute
  8. 2026-09-18 21:16 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 08:36 UTCGHSA enrichment
  11. 2026-09-17 20:13 UTCEG score recompute
  12. 2026-09-17 20:13 UTCGHSA enrichment
  13. 2026-09-17 19:32 UTCEPSS rescore
  14. 2026-09-17 07:47 UTCGHSA enrichment
  15. 2026-09-16 19:23 UTCEG score recompute
  16. 2026-09-16 19:23 UTCGHSA enrichment
  17. 2026-09-16 14:09 UTCEPSS rescore
  18. 2026-09-16 06:58 UTCEG score recompute
  19. 2026-09-16 06:58 UTCGHSA enrichment
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-15 18:35 UTCEG score recompute
  22. 2026-09-15 18:35 UTCGHSA enrichment
  23. 2026-09-15 18:31 UTCNVD updateCVSS v4 → 5.5
  24. 2026-09-15 17:28 UTCEG score recompute
  25. 2026-09-15 17:28 UTCGHSA enrichment
Show 11 more
  1. 2026-09-15 17:28 UTCMITRE cvelistV5CVSS v4 → 6.9
  2. 2026-09-15 09:29 UTCEG score recompute
  3. 2026-09-15 09:29 UTCGHSA enrichment
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-14 21:05 UTCGHSA enrichment
  6. 2026-09-14 15:44 UTCEG score recompute
  7. 2026-09-14 15:44 UTCGHSA enrichment
  8. 2026-09-14 03:20 UTCEG score recompute
  9. 2026-09-14 03:20 UTCNVD updateCVSS v4 → 5.5
  10. 2026-09-14 02:41 UTCEG score recompute
  11. 2026-09-14 02:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-90617?
CVE-2026-90617 is a high vulnerability published on September 14, 2026. A vulnerability was detected in GH05TCREW PentestAgent up to cf882dabea3ed91cef016cdd115e5426315665a2. This vulnerability affects the function run_task of the file interface/main.py of the component MCP HTTP Server. Performing a manipulation results in os command injection. The attack is possible…
When was CVE-2026-90617 disclosed?
CVE-2026-90617 was first published in the National Vulnerability Database on September 14, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90617 actively exploited?
CVE-2026-90617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 25.3% of all scored CVEs.
What is the CVSS score of CVE-2026-90617?
CVE-2026-90617 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-90617?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-90617, 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-90617

Explore →

Is Your Infrastructure Affected by CVE-2026-90617?

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