CVE-2026-103663

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 sources updated this week
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.4Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Ollama is vulnerable to path traversal in the /api/pull endpoint due to insufficient validation of layer digests by the digestToPath function. An unauthenticated remote attacker can specify a path traversal sequence as a layer digest, causing a malicious binary to be written outside the model store. 

Critically if the server process has write access to /usr/lib/ollama (the default in most Ollama Docker images), an attacker can write the malicious file to that directory. On the next server restart, the file is loaded and executed, resulting in remote code execution as root.

This issue was fixed in version 0.35.0.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
43
EG Risk 43/100CISA SSVC

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
Severity94% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 8, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Fix named in the CVE record.
generic

Ollama

https://ollama.com/
genericMentions a patch (unverified)

Vulnerability in Ollama software | CERT Polska

https://cert.pl/en/posts/2026/10/CVE-2026-103663/

Vendor Advisories for CVE-2026-103663(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 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-09 22:53 UTCEG score recompute
  2. 2026-10-09 22:53 UTCGHSA enrichment
  3. 2026-10-09 20:06 UTCEPSS rescore
  4. 2026-10-09 19:04 UTCGHSA enrichment
  5. 2026-10-09 15:17 UTCGHSA enrichment
  6. 2026-10-09 11:29 UTCGHSA enrichment
  7. 2026-10-09 07:41 UTCGHSA enrichment
  8. 2026-10-09 03:53 UTCGHSA enrichment
  9. 2026-10-09 00:04 UTCGHSA enrichment
  10. 2026-10-08 20:16 UTCGHSA enrichment
  11. 2026-10-08 19:34 UTCGHSA enrichment
  12. 2026-10-08 14:38 UTCEG score recompute▲ 2.50
  13. 2026-10-08 14:17 UTCNVD updateCVSS v3 → 9.4 · CVSS v4 → 9.4 · severity → CRITICAL
  14. 2026-10-08 13:38 UTCEG score recompute
  15. 2026-10-08 13:36 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-103663?
CVE-2026-103663 is a critical vulnerability published on October 8, 2026. Ollama is vulnerable to path traversal in the /api/pull endpoint due to insufficient validation of layer digests by the digestToPath function. An unauthenticated remote attacker can specify a path traversal sequence as a layer digest, causing a malicious binary to be written outside the model…
When was CVE-2026-103663 disclosed?
CVE-2026-103663 was first published on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-103663 actively exploited?
CVE-2026-103663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103663?
CVE-2026-103663 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103663?
The CVE record for CVE-2026-103663 names the fix: "This issue was fixed in version 0.35.0." The vendor advisories EchelonGraph has for CVE-2026-103663 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-103663?

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

Book a Demo →Browse All CVEs