CVSS 4.0
9.2 criticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCritical (9.2) in ggml-org llama.cpp. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-107183 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107183?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107183?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107183 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| ggml-org llama.cpp | from b8227 before b11393 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | llama.cpp | no fix listed | DEBIAN-CVE-2026-107183 |
| Ubuntu | 26.04:LTS, 26.10 | llama.cpp | no fix listed | UBUNTU-CVE-2026-107183 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Important.
Red Hat has rated this vulnerability as Critical because unauthenticated remote attackers can cause memory corruption without requiring prior privileges or user interaction. When the inference service processes untrusted HTTP completion requests, malformed chat parser payloads can cause an application crash or enable arbitrary code execution within the host environment. Deployments that run the component strictly in offline batch modes or isolate API endpoints from untrusted network traffic experience significantly reduced risk.
Restrict network exposure of the llama-server service to trusted network segments or localhost using firewall rules or reverse proxy controls.
1. Restrict access to the service port using firewalld:
firewall-cmd --permanent --zone=public --remove-port=8080/tcp
firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_RANGE>
firewall-cmd --reload
Alternatively, configure the server daemon to bind exclusively to the localhost interface (127.0.0.1) if remote connectivity is not required.
Caveats: Limiting network reachability prevents untrusted remote clients from sending completion requests, which will impact external integrations and client applications that rely on remote API access.
Warning: Reloading firewall rules or restarting the service daemon will terminate active network connections and interrupt ongoing inference jobs.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107183.