Skip to content
Noroxi
CVE-2024-39720· NVD / CVE Program· CNA mitre

An issue was discovered in Ollama before 0.1.46.

Noroxi assessment

Priority: Monitor (action score 33/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: github.com/ollama/ollama (Go) 0.1.46; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20241101T215616-1.1; govulncheck-vulndb (SUSE:Linux Enterprise Module for Package Hub 15 SP5) 0.0.20241104T154416-150000.1.12.1.

Low priority for now. Upgrade to github.com/ollama/ollama (Go) 0.1.46; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20241101T215616-1.1; govulncheck-vulndb (SUSE:Linux Enterprise Module for Package Hub 15 SP5) 0.0.20241104T154416-150000.1.12.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue was discovered in Ollama before 0.1.46. An attacker can use two HTTP requests to upload a malformed GGUF file containing just 4 bytes starting with the GGUF custom magic header. By leveraging a custom Modelfile that includes a FROM statement pointing to the attacker-controlled blob file, the attacker can crash the application through the CreateModel route, leading to a segmentation fault (signal SIGSEGV: segmentation violation).

HighCVSS 8.2 · v3.1—No exploit Fix available
Published
Oct 31, 2024
Updated
Jun 17, 2026
EPSS
2.4% · 84th percentile

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
32 / 40 · 8.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.4%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-39720

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
ollamaollama

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • ollama ollamabefore 0.1.46

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/ollama/ollamabefore 0.1.460.1.46
openSUSE:Tumbleweedgovulncheck-vulndbbefore 0.0.20241101T215616-1.10.0.20241101T215616-1.1
SUSE:Linux Enterprise Module for Package Hub 15 SP5govulncheck-vulndbbefore 0.0.20241104T154416-150000.1.12.10.0.20241104T154416-150000.1.12.1
SUSE:Linux Enterprise Module for Package Hub 15 SP5govulncheck-vulndbbefore 0.0.20241104T154416-150000.1.12.10.0.20241104T154416-150000.1.12.1
SUSE:Package Hub 12govulncheck-vulndbbefore 0.0.20241104T154416-5.10.0.20241104T154416-5.1

Other highest-scoring records for the same primary product.

  • CVE-2024-37032Ollama before 0.1.34 does not validate the format of the digest (sha256 with 64 hex digits) when getting the model path, and thus mishandles
    62This week
  • CVE-2026-42249Remote Code Execution in Ollama via Update Mechanism
    40Plan
  • CVE-2026-42248Missing Signature Verification for Updates in Ollama
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-45436Aug 28, 2024 · extractFromZipFile in model.go in Ollama before 0.1.47 can extract members of a ZIP archive outside of the parent directory.
    31Monitor
  • ← EarlierCVE-2024-39719Oct 31, 2024 · An issue was discovered in Ollama through 0.3.14.
    31Monitor
  • Later →CVE-2024-39721Oct 31, 2024 · An issue was discovered in Ollama before 0.1.34.
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/ollama/ollama0.1.46Package registry (OSV)
opensuse:govulncheck-vulndb0.0.20241104T154416-150000.1.12.1 · openSUSE:Leap 15.5Package registry (OSV)
suse:govulncheck-vulndb0.0.20241104T154416-150000.1.12.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-12055140 days apartDoS using malicious gguf model file in ollama/ollama
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records