A vulnerability was determined in ggml-org llama.cpp bec4772f6. This affects the function rpc_server::graph_compute of the file ggml/src/ggml-rpc/ggml-rpc.cpp of the component ggml-RPC Server. Executing a manipulation can lead to null pointer dereference. The attack may be launched remotely. The pull request to fix this issue awaits acceptance.
CVE-2026-78148
Score 5.3 from GitHub Security Advisory published 2026-08-24. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
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 computedSeverity53% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
August 23, 2026
Last Modified
August 24, 2026
Advisory Details (3)
Auto-updated Aug 23, 2026GitHub - ggml-org/llama.cpp: LLM inference in C/C++ · GitHub
https://github.com/ggml-org/llama.cpp/rpc : reject invalid top-level graph nodes in graph_compute
Upstream fix in progress (PR #25670 · ggml-org/llama.cpp, state=open)
https://github.com/ggml-org/llama.cpp/pull/25670Remote unauthenticated NULL-pointer dereference in ggml-rpc graph_compute() via a node id of 0 (ggml_graph_plan/ggml_is_empty) · Issue #25299 · ggml-org/llama.cpp · GitHub
https://github.com/ggml-org/llama.cpp/issues/25299Vendor Advisories for CVE-2026-78148(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 17:36 UTCEG score recompute
- 2026-08-29 17:36 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 17:48 UTCGHSA enrichment
- 2026-08-27 18:16 UTCEG score recompute
- 2026-08-27 18:16 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 17:49 UTCEG score recompute
- 2026-08-26 17:49 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 17:48 UTCEG score recompute
- 2026-08-25 17:48 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 18:24 UTCEG score recompute
- 2026-08-24 18:24 UTCGHSA enrichment
- 2026-08-24 18:02 UTCEG score recompute
- 2026-08-24 18:01 UTCGHSA enrichment
- 2026-08-24 16:46 UTCEG score recompute
- 2026-08-24 16:46 UTCGHSA enrichment
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-24 00:35 UTCEG score recompute
- 2026-08-24 00:35 UTCGHSA enrichment
- 2026-08-23 23:21 UTCEG score recompute
- 2026-08-23 23:20 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-78148?
When was CVE-2026-78148 disclosed?
Is CVE-2026-78148 actively exploited?
What is the CVSS score of CVE-2026-78148?
How do I remediate CVE-2026-78148?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78148
Is Your Infrastructure Affected by CVE-2026-78148?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.