A vulnerability has been found in Ollama up to 0.34.1. The affected element is the function IsValid of the file types/model/name.go of the component Pull API. The manipulation leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 0.34.2 is sufficient to fix this issue. The identifier of the patch is dfabde4539e42ba1e1eab50a3a50b88aea7958a0. It is suggested to upgrade the affected component.
CVE-2026-108836
HIGHPre-NVD 7.37.3Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.3 from GitHub Security Advisory published 2026-10-12. A secondary CVSS source baseline 7.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
7.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).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.3
- EG Score
- 7.3HIGHhigh confidence
- EG Risk
- 48EG Risk 48/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)Severity73% × 45%The EG Score, 7.3 of 10.Exploitation0.5% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.5%
- EPSS %ILE
- 38th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (6)
Auto-updated Oct 12, 2026Patch available. Sources: github_release, github_commit, github_pr.
GitHub release Patch Available
v0.34.2
Patch available: ollama/ollama v0.34.2
https://github.com/ollama/ollama/releases/tag/v0.34.2GitHub pull request
x/transfer, server: tighten redirect handling for registry requests
Fix merged in ollama/ollama PR #18512 on 2026-09-17 — awaiting tagged release
https://github.com/ollama/ollama/pull/18512GitHub commit
commit dfabde4539e4 (ollama/ollama)
Fix landed in ollama/ollama commit dfabde4539e4 — awaiting tagged release
https://github.com/ollama/ollama/commit/dfabde4539e42ba1e1eab50a3a50b88aea7958a0Web page
GitHub - ollama/ollama: Get up and running with Kimi, GLM, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models. · GitHub
https://github.com/ollama/ollama/Web page
test/test.pdf at main · aLtEr6/test · GitHub
https://github.com/aLtEr6/test/blob/main/test.pdfVendor Advisories for CVE-2026-108836(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 14× in last 7d / 14× 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 19:53 UTCEG score recompute
- 2026-10-13 19:53 UTCGHSA enrichmentGHSA-fr42-jr2w-mx59 · GitHub CVSS 7.3
- 2026-10-13 19:24 UTCNVD updateCVSS v4 → 5.5
- 2026-10-13 19:01 UTCEG score recompute
- 2026-10-13 19:00 UTCGHSA enrichmentGHSA-fr42-jr2w-mx59 · GitHub CVSS 7.3
- 2026-10-13 18:59 UTCMITRE cvelistV5CVSS v4 → 6.9
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
- 2026-10-13 13:48 UTCEG score recompute
- 2026-10-13 13:48 UTCGHSA enrichmentGHSA-fr42-jr2w-mx59 · GitHub CVSS 7.3
- 2026-10-13 13:45 UTCNVD updateCVSS v4 → 5.5
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 13:24 UTCNVD updateCVSS v4 → 5.5
- 2026-10-12 13:18 UTCEG score recomputeFirst assessed: 7.3 HIGH
- 2026-10-12 13:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108836?
CVE-2026-108836 is a high-severity vulnerability; its CVE record was published on October 12, 2026. A vulnerability has been found in Ollama up to 0.34.1. The affected element is the function IsValid of the file types/model/name.go of the component Pull API. The manipulation leads to server-side request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the…
When was the CVE record for CVE-2026-108836 published?
The CVE record for CVE-2026-108836 was published on October 12, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-108836 actively exploited?
CVE-2026-108836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108836?
CVE-2026-108836 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108836?
A fix for CVE-2026-108836 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-108836 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108836
Is Your Infrastructure Affected by CVE-2026-108836?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.