CVE-2026-46711

HIGHPre-NVD 8.38.3
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th 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-90085 (ENISA EUVD)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule 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.3%CVSS: 8.3Exploit: No code on recordExposed services: Not assessed

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

Soft Machine is a Virtual Machine–based agentic development environment / Cloud OS. In versions 0.2.247 and prior, the workspace HTTP service that listens on 0.0.0.0:8080 inside each sm-ws-* Fly Machine exposes endpoints (/health, /file/, /archive/) without any authentication or origin check. Any host that can reach TCP/8080 on a workspace can read arbitrary files under that workspace's /workspace root and download whole project trees as tar archives. Because every workspace shares the same Fly private 6PN and resolves all peer addresses via the unauthenticated _instances.internal TXT record, every other sm-ws-* machine on the same Fly app/org is a reachable, unauthenticated attacker — the trust boundary (workspace owner ↔ everyone-else) is missing. At time of publication, there are no publicly known patches.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
53
EG Risk 53/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)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (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 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: No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
19th
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 (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is its impact severity (EG Severity), not escalated.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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.

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule at low or medium mission impact and sooner than that at high.

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

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

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

September 30, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 30, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Unauthenticated workspace API exposes arbitrary file read & directory exfiltration to any peer on the Fly private network · Advisory · Soft-Machine-io/security · GitHub

https://github.com/Soft-Machine-io/security/security/advisories/GHSA-h6g6-qr45-qmrr

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 46× 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-01 19:17 UTCEG score recompute
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-25 14:25 UTCEG score recompute
  11. 2026-10-25 04:13 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-18 03:36 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-17 13:10 UTCEG score recompute
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 29 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-12 16:02 UTCEG score recompute
  3. 2026-10-11 19:45 UTCEG score recompute
  4. 2026-10-11 16:59 UTCEG score recompute
  5. 2026-10-11 14:24 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-10 20:02 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-10 08:03 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-08 20:04 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-08 08:00 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-06 20:01 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-05 20:03 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-05 08:04 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-03 20:02 UTCEG score recompute
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-10-02 19:59 UTCEG score recompute
  24. 2026-10-01 20:00 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  26. 2026-09-30 18:26 UTCEG score recompute
  27. 2026-09-30 17:21 UTCEG score recompute
  28. 2026-09-30 16:32 UTCEG score recomputeFirst assessed: 8.3 HIGH
  29. 2026-09-30 16:31 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46711?
CVE-2026-46711 is a high-severity vulnerability; its CVE record was published on September 30, 2026. Soft Machine is a Virtual Machine–based agentic development environment / Cloud OS. In versions 0.2.247 and prior, the workspace HTTP service that listens on 0.0.0.0:8080 inside each sm-ws-* Fly Machine exposes endpoints (/health, /file/<path>, /archive/<dir>) without any authentication or origin…
When was the CVE record for CVE-2026-46711 published?
The CVE record for CVE-2026-46711 was published on September 30, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-46711 actively exploited?
CVE-2026-46711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46711?
CVE-2026-46711 has a CVSS base score of 8.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46711?
No fix for CVE-2026-46711 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-46711?

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

Book a Demo →Browse All CVEs