CVE-2026-67531

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-53684 (ENISA EUVD)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

FrontMCP is a TypeScript-first framework for the Model Context Protocol (MCP). Prior to 1.5.7, the sandboxed codecall:execute tool exposes live host Zod schema instances to the script via getTool(), and because Zod v4 defines _zod as a non-configurable, non-writable own property, the ECMAScript Proxy invariants force the security membrane to hand back the raw host object, letting a script reach _zod.constr.constructor (the host Function constructor) and execute arbitrary code in the server process. A single tools/call is sufficient to escape the sandbox and achieve remote code execution as the server user, exposing everything the process holds such as OAuth client secrets, JWT_SECRET, session keys, database credentials, and cloud instance metadata. Because the framework's DEFAULT_AUTH_OPTIONS is public mode, an unconfigured server serves this to unauthenticated callers, and on authenticated servers an indirect prompt injection in tool output or fetched content can trigger it without a human attackerThis issue is fixed in version 1.5.7.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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.

The score's inputs: 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

August 5, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Oct 3, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

CodeCall sandbox escape to host RCE via live Zod schema exposed by getTool · Advisory · agentfront/frontmcp · GitHub

https://github.com/agentfront/frontmcp/security/advisories/GHSA-mp29-fxh8-92px
GitHub commit Patch Available

commit 209cddd19a8d (agentfront/frontmcp)

Patch available: agentfront/frontmcp v1.5.7 (contains commit 209cddd19a8d)

https://github.com/agentfront/frontmcp/commit/209cddd19a8d4db0777f725b527818da7df6f67f

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 183 rows 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 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-11-13 02:53 UTCEchelonGraph re-scored
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-11-12 04:49 UTCEchelonGraph re-scored
  5. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-11-11 06:45 UTCEchelonGraph re-scored
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-10 08:40 UTCEchelonGraph re-scored
  9. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-11-09 10:36 UTCEchelonGraph re-scored
  11. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  12. 2026-11-08 12:32 UTCEchelonGraph re-scored
  13. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  14. 2026-11-07 14:27 UTCEchelonGraph re-scored
  15. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  16. 2026-11-06 15:55 UTCOSV refresh
  17. 2026-11-05 18:14 UTCEchelonGraph re-scored
  18. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  19. 2026-11-04 20:10 UTCEchelonGraph re-scored
  20. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  21. 2026-11-03 22:05 UTCEchelonGraph re-scored
  22. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  23. 2026-11-02 23:59 UTCEchelonGraph re-scored
  24. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  25. 2026-11-02 01:54 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-11-01 03:51 UTCEchelonGraph re-scored
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-10-31 05:47 UTCEchelonGraph re-scored
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-10-30 07:42 UTCEchelonGraph re-scored
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-10-29 09:37 UTCEchelonGraph re-scored
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-10-28 11:33 UTCEchelonGraph re-scored
  11. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  12. 2026-10-27 10:45 UTCEchelonGraph re-scored
  13. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  14. 2026-10-26 12:41 UTCEchelonGraph re-scored
  15. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  16. 2026-10-25 14:10 UTCEchelonGraph re-scored
  17. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-23 21:26 UTCEchelonGraph re-scored
  19. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-23 00:48 UTCEchelonGraph re-scored
  21. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-22 01:56 UTCEchelonGraph re-scored
  23. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-21 03:48 UTCEchelonGraph re-scored
  25. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  26. 2026-10-20 05:27 UTCEchelonGraph re-scored
  27. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-19 06:52 UTCEchelonGraph re-scored
  29. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  30. 2026-10-18 03:20 UTCEchelonGraph re-scored
  31. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-17 06:11 UTCEchelonGraph re-scored
  33. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-10-16 07:16 UTCEchelonGraph re-scored
  35. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  36. 2026-10-15 06:11 UTCEchelonGraph re-scored
  37. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  38. 2026-10-14 01:47 UTCEchelonGraph re-scored
  39. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  40. 2026-10-12 21:59 UTCEchelonGraph re-scored
  41. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  42. 2026-10-12 15:45 UTCEchelonGraph re-scored
  43. 2026-10-11 19:30 UTCEchelonGraph re-scored
  44. 2026-10-11 16:46 UTCEchelonGraph re-scored
  45. 2026-10-11 14:06 UTCEchelonGraph re-scored
  46. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  47. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  48. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  49. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  50. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  51. 2026-10-06 23:36 UTCEchelonGraph re-scored
  52. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  53. 2026-10-05 19:32 UTCEchelonGraph re-scored
  54. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  55. 2026-10-04 23:29 UTCEchelonGraph re-scored
  56. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  57. 2026-10-04 05:57 UTCEchelonGraph re-scored
  58. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  59. 2026-10-03 01:07 UTCEchelonGraph re-scored
  60. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-10-02 09:50 UTCEchelonGraph re-scored
  62. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  63. 2026-10-01 01:52 UTCEchelonGraph re-scored
  64. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  65. 2026-09-29 06:07 UTCEchelonGraph re-scored
  66. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  67. 2026-09-27 17:38 UTCEchelonGraph re-scored
  68. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  69. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  70. 2026-09-25 04:29 UTCEchelonGraph re-scored
  71. 2026-09-23 21:20 UTCEchelonGraph re-scored
  72. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  73. 2026-09-22 21:22 UTCEchelonGraph re-scored
  74. 2026-09-22 01:22 UTCEchelonGraph re-scored
  75. 2026-09-20 20:46 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-67531?
CVE-2026-67531 is a critical-severity vulnerability; its CVE record was published on August 5, 2026. FrontMCP is a TypeScript-first framework for the Model Context Protocol (MCP). Prior to 1.5.7, the sandboxed codecall:execute tool exposes live host Zod schema instances to the script via getTool(), and because Zod v4 defines _zod as a non-configurable, non-writable own property, the ECMAScript…
When was the CVE record for CVE-2026-67531 published?
The CVE record for CVE-2026-67531 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-67531 actively exploited?
CVE-2026-67531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67531?
CVE-2026-67531 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67531?
A fix for CVE-2026-67531 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-67531?

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