A vulnerability has been found in EricLBuehler mistral.rs up to 0.9.3. Impacted is the function is_global_ip of the file mistralrs-server-core/src/media_source.rs. Such manipulation of the argument ip leads to server-side request forgery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 0.9.4 is recommended to address this issue. The name of the patch is cfb8c6a0c42361dc4579a9110b54d339c255b9fd. The affected component should be upgraded.
CVE-2026-108939
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.3 from GitHub Security Advisory published 2026-10-13. A secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMhigh confidence
- EG Risk
- 24EG Risk 24/100
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 (value × EchelonGraph’s weight)Severity53% × 45%The EG Score, 5.3 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
- 39th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (5)
Auto-updated Oct 12, 2026GitHub - EricLBuehler/mistral.rs: Fast, flexible LLM inference · GitHub
https://github.com/EricLBuehler/mistral.rs/v0.9.4
Patch available: EricLBuehler/mistral.rs v0.9.4
https://github.com/EricLBuehler/mistral.rs/releases/tag/v0.9.4commit cfb8c6a0c423 (EricLBuehler/mistral.rs)
Fix landed in EricLBuehler/mistral.rs commit cfb8c6a0c423 — awaiting tagged release
https://github.com/EricLBuehler/mistral.rs/commit/cfb8c6a0c42361dc4579a9110b54d339c255b9fdfix(server): judge IPv6 transition addresses by their embedded IPv4 in the media guard
Fix merged in EricLBuehler/mistral.rs PR #2446 on 2026-09-24 — awaiting tagged release
https://github.com/EricLBuehler/mistral.rs/pull/2446commit cfb8c6a0c (EricLBuehler/mistral.rs)
Fix landed in EricLBuehler/mistral.rs commit cfb8c6a0c — awaiting tagged release
https://github.com/EricLBuehler/mistral.rs/commit/cfb8c6a0cVendor Advisories for CVE-2026-108939(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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.
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-13 13:56 UTCEG score recompute
- 2026-10-13 13:56 UTCGHSA enrichmentGHSA-qjg5-pf8f-r356 · GitHub CVSS 5.3
- 2026-10-13 00:27 UTCEG score recompute
- 2026-10-13 00:24 UTCNVD updateCVSS v4 → 5.5
- 2026-10-12 23:26 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
- 2026-10-12 23:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108939?
When was the CVE record for CVE-2026-108939 published?
Is CVE-2026-108939 actively exploited?
What is the CVSS score of CVE-2026-108939?
How do I remediate CVE-2026-108939?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108939
Is Your Infrastructure Affected by CVE-2026-108939?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.