CVE-2026-120308

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-114842 (ENISA EUVD) · GHSA-92w2-g272-fr77 (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
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.5%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (JFrog) states them: "Upgrade the gateway to 0.1.776 or later and the worker to 0.1.756 or later."

A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker's filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker's files, including other tenants' volumes stored on that machine. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace.

CVSS v3
9.9
EG Score
9.9CRITICALhigh 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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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.5%
EPSS %ILE
45th
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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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 (7)

Auto-updated Nov 2, 2026
Patch available. Sources: github_commit, github_pr, github_release.
GitHub release Patch Available

Worker: 0.1.756

Patch available: beam-cloud/beta9 worker-0.1.756

https://github.com/beam-cloud/beta9/releases/tag/worker-0.1.756
GitHub release Patch Available

Worker: 0.1.745

Patch available: beam-cloud/beta9 worker-0.1.745

https://github.com/beam-cloud/beta9/releases/tag/worker-0.1.745
GitHub release Patch Available

Gateway: 0.1.776

Patch available: beam-cloud/beta9 gateway-0.1.776

https://github.com/beam-cloud/beta9/releases/tag/gateway-0.1.776
GitHub release Patch Available

Gateway: 0.1.769

Patch available: beam-cloud/beta9 gateway-0.1.769

https://github.com/beam-cloud/beta9/releases/tag/gateway-0.1.769
GitHub pull request Patch Available

Handle sandbox edge cases

Patch available: beam-cloud/beta9 worker-0.1.806 (PR #1897 merged 2026-09-15)

https://github.com/beam-cloud/beta9/pull/1897
GitHub commit Patch Available

commit a28bf12cf000 (beam-cloud/beta9)

Patch available: beam-cloud/beta9 worker-0.1.806 (contains commit a28bf12cf000)

https://github.com/beam-cloud/beta9/commit/a28bf12cf0007c792a25d8ed282b4e8bf6f30393
Web page

GitHub - beam-cloud/beta9: Ultrafast serverless GPU inference, sandboxes, and background jobs · GitHub

https://github.com/beam-cloud/beta9

Vendor Advisories for CVE-2026-120308(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 13× in last 7d / 27× 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 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). "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.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-12 12:57 UTCEchelonGraph re-scored
  3. 2026-11-12 12:57 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-11 11:08 UTCEchelonGraph re-scored
  6. 2026-11-11 11:08 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-11-10 09:18 UTCEchelonGraph re-scored
  9. 2026-11-10 09:18 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-11-09 07:29 UTCEchelonGraph re-scored
  12. 2026-11-09 07:29 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-08 05:40 UTCEchelonGraph re-scored
  15. 2026-11-08 05:40 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-11-07 03:50 UTCEchelonGraph re-scored
  18. 2026-11-07 03:50 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  19. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-11-06 02:01 UTCEchelonGraph re-scored
  21. 2026-11-06 02:01 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  22. 2026-11-05 23:55 UTCOSV refresh
  23. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-11-05 00:12 UTCEchelonGraph re-scored
  25. 2026-11-05 00:12 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
Show 17 more
  1. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-03 22:22 UTCEchelonGraph re-scored
  3. 2026-11-03 22:22 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-02 20:26 UTCEchelonGraph re-scored
  6. 2026-11-02 20:26 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-02 19:53 UTCEchelonGraph re-scored
  8. 2026-11-02 19:53 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-11-02 19:46 UTCEchelonGraph re-scored
  10. 2026-11-02 19:46 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  11. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-11-02 15:15 UTCEchelonGraph re-scored
  13. 2026-11-02 15:15 UTCGHSA enrichmentGHSA-92w2-g272-fr77 · GitHub severity CRITICAL · GitHub CVSS 9.9
  14. 2026-11-01 14:02 UTCENISA EUVD ID recordedEUVD-2026-114842 · Source: ENISA EUVD
  15. 2026-11-01 13:26 UTCEchelonGraph re-scored
  16. 2026-11-01 13:04 UTCEchelonGraph re-scoredFirst assessed: 9.9 CRITICAL
  17. 2026-11-01 13:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-120308?
CVE-2026-120308 is a critical-severity vulnerability; its CVE record was published on November 1, 2026. A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace…
When was the CVE record for CVE-2026-120308 published?
The CVE record for CVE-2026-120308 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-120308 actively exploited?
CVE-2026-120308 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120308?
CVE-2026-120308 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-120308?
A fix for CVE-2026-120308 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (JFrog) states them: "Upgrade the gateway to 0.1.776 or later and the worker to 0.1.756 or later." The vendor advisories EchelonGraph has for CVE-2026-120308 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-120308?

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