VULNpocalypse

CVE-2026-108836: Ollama Pull API name.go IsValid server-side request forgery

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by VulDB, published 2026-10-12).

Weakness: Server-Side Request Forgery

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Also known as: EUVD-2026-97364, GHSA-fr42-jr2w-mx59

VEDAS cluster: VEDAS:DIVERGEDAWN

Exploit Observer links 5 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (5)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (3)

Catalogue entries, not exploit evidence.

3 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.005
low predicted chance of attack
VEDAS
0.985
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
Ollamaversion 0.34.0
version 0.34.1		0.34.2 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

How to detect it

Nuclei template (active check)

Ollama - Pull API Server-Side Request Forgery

Ollama up to and including 0.34.1 fails to properly validate model names in the IsValid function of types/model/name.go, which backs the unauthenticated Pull API. The host component of a crafted model name is used as the registry endpoint without restriction, so a request to POST /api/pull with a model name whose host points at an attacker-controlled or internal address causes the Ollama server to issue a request to that host (server-side request forgery). This template sends a safe pull request whose model host is an out-of-band collaborator domain and detects the resulting interaction. Fixed in 0.34.2.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /api/pull); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using word matchers. Severity in the template: medium. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-108836.yaml
Show the template (42 lines)
yaml
id: CVE-2026-108836

info:
  name: "Ollama - Pull API Server-Side Request Forgery"
  author: vedas-arpsyndicate
  severity: medium
  description: |
    Ollama up to and including 0.34.1 fails to properly validate model names in the IsValid function of
    types/model/name.go, which backs the unauthenticated Pull API. The host component of a crafted model
    name is used as the registry endpoint without restriction, so a request to POST /api/pull with a
    model name whose host points at an attacker-controlled or internal address causes the Ollama server
    to issue a request to that host (server-side request forgery). This template sends a safe pull
    request whose model host is an out-of-band collaborator domain and detects the resulting interaction.
    Fixed in 0.34.2.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-108836&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=ollama&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
    cvss-score: 6.3
    cve-id: CVE-2026-108836
    cwe-id: CWE-918
  metadata:
    verified: false
    max-request: 1
  tags: cve,cve2026,ollama,ssrf,oast

http:
  - raw:
      - |
        POST /api/pull HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"model":"{{interactsh-url}}/library/alpine","insecure":true,"stream":false}

    matchers-condition: and
    matchers:
      - type: word
        part: interactsh_protocol
        words:
          - "dns"

CVE-2026-108836.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-108836 Ollama - Pull API Server-Side Request Forgery. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HOME_NET any (msg:"VEDAS CVE-2026-108836 Ollama - Pull API Server-Side Request Forgery"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/pull"; nocase; fast_pattern; http.request_body; content:"\"model\""; pcre:"/\"model\"\s*:\s*\"[^\"\/]+\.[^\"\/]+\//"; classtype:web-application-attack; reference:cve,CVE-2026-108836; reference:url,https://www.exploit.observer/?keyword=CVE-2026-108836&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=ollama&match=exact; sid:1076201; rev:1;)

CVE-2026-108836.rules on GitHub

References

Vendor advisories and patches

Exploits and technical analysis

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.