VulnerabilityPublished 31 Oct 2024Updated 1 Nov 2024

CVE-2024-39719: ollama · Generation of Error Message Containing Sensitive Information

Affects ollamaSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.3.15 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 4.2% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.3.15

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade ollama to 0.3.15.

Affected software

Product	Affected	Fixed in
npmollama`pkg:npm/ollama`Other threats	Affected <0.3.15	Fixed in 0.3.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-39719, organizations should implement the following specific measures: 1) Restrict access to the api/create endpoint by implementing network-level controls such as IP whitelisting, VPN access, or firewall rules to limit exposure to trusted users only. 2) Employ web application firewalls (WAFs) configured to detect and block requests with suspicious path parameters or error message patterns indicative of probing attempts. 3) Monitor application logs for repeated or anomalous requests to the CreateModel route that may indicate reconnaissance activity. 4) Implement custom error handling in Ollama to avoid disclosing detailed error messages; replace explicit "File does not exist" responses with generic error messages that do not reveal file existence. 5) Stay updated with Ollama vendor advisories and apply patches promptly once available. 6) Conduct regular security assessments and penetration testing to identify similar information disclosure issues. 7) Consider deploying runtime application self-protection (RASP) solutions to detect and mitigate exploitation attempts in real time. These targeted actions go beyond generic advice by focusing on access control, error message management, and proactive detection tailored to this vulnerability.

Description

An issue was discovered in Ollama through 0.3.14. File existence disclosure can occur via api/create. When calling the CreateModel route with a path parameter that does not exist, it reflects the "File does not exist" error message to the attacker, providing a primitive for file existence on the server.

Impact

The primary impact of CVE-2024-39719 is the disclosure of sensitive information about the server's file system through error messages. This can aid attackers in mapping the server environment, identifying existing files, and planning further attacks. While the vulnerability does not directly compromise data integrity or availability, the confidentiality breach can be a stepping stone for more severe exploits, especially in complex environments where file paths may reveal configuration files, credentials, or other sensitive resources. Organizations using Ollama in exposed environments risk targeted attacks that leverage this reconnaissance. The lack of authentication requirements and the ability to exploit remotely increase the risk profile. However, since no direct code execution or data modification is possible solely through this vulnerability, the immediate damage is limited to information disclosure. The absence of known exploits in the wild reduces the current threat level but does not eliminate future risk. Overall, the vulnerability can facilitate lateral movement, privilege escalation, or exploitation of chained vulnerabilities in affected systems.

CWE-209Generation of Error Message Containing Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Implementation · Attack Surface Reduction
Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
Padding Oracle Crypto Attack (opens in a new tab)
Query System for Information (opens in a new tab)
Blind SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

oligo.security/blog/more-models-more-probllms (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:24 UTC

WeaknessesCWE-209

Technical details

References

Community reviews

Related threats