CVE-2026-107183

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-07. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

llama.cpp before b11393 contains a use-after-free and double free vulnerability in common_chat_peg_mapper::map that allows unauthenticated remote attackers to corrupt heap memory via a dangling current_tool pointer. Attackers can submit a chat_parser in a POST /completion request emitting a tool-id after a tool-close tag to crash llama-server and shape a heap write primitive.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/100

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 (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 7, 2026

Last Modified

October 7, 2026

Advisory Details (6)

Auto-updated Oct 7, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
Web page

llama.cpp before b11393 Use-After-Free via common_chat_peg_mapper chat_parser | Advisories | VulnCheck

https://www.vulncheck.com/advisories/llama-cpp-before-b11393-use-after-free-via-common-chat-peg-mapper-chat-parser
Web page

GitHub - ggml-org/llama.cpp: LLM inference in C/C++ · GitHub

https://github.com/ggml-org/llama.cpp
Web page

llama.cpp/tools/server/server-schema.cpp at bed0a856606ee4a24a164066f73d2379447033f5 · ggml-org/llama.cpp · GitHub

https://github.com/ggml-org/llama.cpp/blob/bed0a856606ee4a24a164066f73d2379447033f5/tools/server/server-schema.cpp#L321-L324
Web page

llama.cpp/common/chat-peg-parser.cpp at bed0a856606ee4a24a164066f73d2379447033f5 · ggml-org/llama.cpp · GitHub

https://github.com/ggml-org/llama.cpp/blob/bed0a856606ee4a24a164066f73d2379447033f5/common/chat-peg-parser.cpp#L343-L355
GitHub commit

commit dbe4c3ed4234 (ggml-org/llama.cpp)

Fix landed in ggml-org/llama.cpp commit dbe4c3ed4234 — awaiting tagged release

https://github.com/ggml-org/llama.cpp/commit/dbe4c3ed42343f0a7ba0fd7e808ffeaca404d29f
GitHub pull request

chat-peg-parser : fix use-after-free / double-free in common_chat_peg_mapper

Fix merged in ggml-org/llama.cpp PR #29942 on 2026-10-04 — awaiting tagged release

https://github.com/ggml-org/llama.cpp/pull/29942

Vendor Advisories for CVE-2026-107183(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
llama.cpp10108+dfsg-1 ... 9951+dfsg-3 (59 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 20:13 UTCEG score recompute
  2. 2026-10-11 20:13 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  3. 2026-10-11 18:26 UTCEG score recompute
  4. 2026-10-11 15:00 UTCEG score recompute
  5. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-11 09:11 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  7. 2026-10-10 22:12 UTCEG score recompute
  8. 2026-10-10 22:12 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-10 11:10 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  11. 2026-10-10 00:12 UTCEG score recompute
  12. 2026-10-10 00:12 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-09 13:12 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  15. 2026-10-09 02:12 UTCEG score recompute
  16. 2026-10-09 02:12 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  17. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-08 15:12 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  19. 2026-10-08 03:13 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  20. 2026-10-07 16:12 UTCEG score recompute
  21. 2026-10-07 16:12 UTCGHSA enrichmentGHSA-3g9g-qh2j-c5q8 · GitHub severity CRITICAL · GitHub CVSS 8.1
  22. 2026-10-07 15:30 UTCEG score recompute
  23. 2026-10-07 14:42 UTCEG score recompute
  24. 2026-10-07 14:28 UTCEG score recompute
  25. 2026-10-07 13:52 UTCEG score recomputeFirst assessed: 8.1 HIGH
Show 1 more
  1. 2026-10-07 13:51 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107183?
CVE-2026-107183 is a high-severity vulnerability; its CVE record was published on October 7, 2026. llama.cpp before b11393 contains a use-after-free and double free vulnerability in commonchatpegmapper::map that allows unauthenticated remote attackers to corrupt heap memory via a dangling currenttool pointer. Attackers can submit a chat_parser in a POST /completion request emitting a tool-id…
When was CVE-2026-107183 made public?
CVE-2026-107183 was made public on October 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 7, 2026. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-107183 actively exploited?
CVE-2026-107183 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107183?
CVE-2026-107183 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107183?
An upstream fix for CVE-2026-107183 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-107183 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107183

Explore →

Is Your Infrastructure Affected by CVE-2026-107183?

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

Book a Demo →Browse All CVEs