CVE-2026-120338

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-11-01. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2026-114859 (ENISA EUVD) · GHSA-3g72-rrqc-f76c (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Prefab UI's Generative UI sandbox runs caller-supplied Python inside Pyodide, Python compiled to WebAssembly, in a Deno subprocess. The feature is documented as isolation for untrusted code, including LLM-written UI. From prefab-ui 0.14.0 through 0.20.2 the launcher starts Deno with unrestricted --allow-read, --allow-write, and --allow-net, and the runner leaves the Deno API on the JavaScript global object. Pyodide's js module proxies that global, so the Python can call Deno.readTextFileSync and Deno.writeTextFileSync. A caller who can supply the code can read and write files as the server OS user, and can persist code execution by writing a .pth file into the server virtualenv's site-packages. The usual remote path is FastMCP's GenerativeUI provider, which registers the MCP tool generate_prefab_ui and forwards that tool's code argument into this sandbox. On a FastMCP server with no authentication configured, any client who can reach the server can call the tool. With authentication, any client allowed to call tools can. Generative UI is opt-in, and the host must have Deno installed. Confirmed on prefab-ui 0.20.2. Fixed in 0.21.0: after the runtime and Prefab sources load, the runner revokes Deno read, write, and network permission before it accepts code, the process is started with --no-prompt so a permission request cannot grant them again, and bootstrap network access is limited to cdn.jsdelivr.net. The fix is commit 030f074 (pull request 538).

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
45
EG Risk 45/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.8%
EPSS %ILE
55th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

November 1, 2026

Last Modified

November 2, 2026

Advisory Details (8)

Auto-updated Nov 2, 2026
Patch available. Sources: github_commit, github_pr, github_release.
Web page

prefab-ui · PyPI

https://pypi.org/project/prefab-ui/
GitHub release Patch Available

v0.21.0: UI, Robot

Patch available: PrefectHQ/prefab v0.21.0

https://github.com/PrefectHQ/prefab/releases/tag/v0.21.0
GitHub release Patch Available

v0.20.2: Fine Print

Patch available: PrefectHQ/prefab v0.20.2

https://github.com/PrefectHQ/prefab/releases/tag/v0.20.2
GitHub release Patch Available

v0.14.0: Main Stream

Patch available: PrefectHQ/prefab v0.14.0

https://github.com/PrefectHQ/prefab/releases/tag/v0.14.0
GitHub pull request Patch Available

Refresh dependencies and fix renderer and sandbox regressions

Patch available: PrefectHQ/prefab v0.21.0 (PR #538 merged 2026-10-25)

https://github.com/PrefectHQ/prefab/pull/538
GitHub commit Patch Available

commit 030f074f85e0 (PrefectHQ/prefab)

Patch available: PrefectHQ/prefab v0.21.0 (contains commit 030f074f85e0)

https://github.com/PrefectHQ/prefab/commit/030f074f85e0b1be0dd44b0283185aecb26337a2
Web page

GitHub - PrefectHQ/prefab: 🎨 The generative UI framework that even humans can use. · GitHub

https://github.com/PrefectHQ/prefab

Vendor Advisories for CVE-2026-120338(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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.

  1. 2026-11-02 20:26 UTCEG score recompute
  2. 2026-11-02 20:26 UTCGHSA enrichmentGHSA-3g72-rrqc-f76c · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-11-02 19:53 UTCEG score recompute
  4. 2026-11-02 19:53 UTCGHSA enrichmentGHSA-3g72-rrqc-f76c · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-11-02 19:46 UTCGHSA enrichmentGHSA-3g72-rrqc-f76c · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-11-02 18:41 UTCEG score recompute
  7. 2026-11-02 18:41 UTCGHSA enrichmentGHSA-3g72-rrqc-f76c · GitHub severity CRITICAL · GitHub CVSS 10.0
  8. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-11-01 17:02 UTCENISA EUVD ID recordedEUVD-2026-114859 · Source: ENISA EUVD
  10. 2026-11-01 16:28 UTCEG score recompute
  11. 2026-11-01 15:27 UTCEG score recomputeFirst assessed: 10.0 CRITICAL
  12. 2026-11-01 15:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-120338?
CVE-2026-120338 is a critical-severity vulnerability; its CVE record was published on November 1, 2026. Prefab UI's Generative UI sandbox runs caller-supplied Python inside Pyodide, Python compiled to WebAssembly, in a Deno subprocess. The feature is documented as isolation for untrusted code, including LLM-written UI. From prefab-ui 0.14.0 through 0.20.2 the launcher starts Deno with unrestricted…
When was the CVE record for CVE-2026-120338 published?
The CVE record for CVE-2026-120338 was published on November 1, 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 November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-120338 actively exploited?
CVE-2026-120338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120338?
CVE-2026-120338 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-120338?
A fix for CVE-2026-120338 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-120338 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-120338?

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