A vulnerability was detected in ggml-org llama.cpp d006858/e15efe0. This affects the function _visit_pattern of the file common/json-schema-to-grammar.cpp. The manipulation results in null pointer dereference. The attack can be launched remotely. The pull request to fix this issue awaits acceptance.
CVE-2026-17500
MEDIUMPre-NVD 5.35.3
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 5.3Exploit: None knownExposed: 0
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(low)
- EG Risk
- 28(Track)EG Risk 28/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%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 27, 2026
Last Modified
July 27, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026No patch confirmed yet. Sources: github_pr.
generic
GitHub - ggml-org/llama.cpp: LLM inference in C/C++ · GitHub
https://github.com/ggml-org/llama.cpp/github_pr
json-schema-to-grammar: harden _visit_pattern against malformed regex patterns
Upstream fix in progress (PR #25308 · ggml-org/llama.cpp, state=open)
https://github.com/ggml-org/llama.cpp/pull/25308generic
NULL-pointer dereference in JSON-Schema regex/pattern handling during grammar construction · Issue #25284 · ggml-org/llama.cpp · GitHub
https://github.com/ggml-org/llama.cpp/issues/25284Vendor Advisories for CVE-2026-17500(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 3× in last 7d / 3× 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-07-27 01:23 UTCEG score recompute
- 2026-07-27 01:02 UTCEG score recompute
- 2026-07-27 01:02 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-17500?
CVE-2026-17500 is a medium vulnerability published on July 27, 2026. A vulnerability was detected in ggml-org llama.cpp d006858/e15efe0. This affects the function visitpattern of the file common/json-schema-to-grammar.cpp. The manipulation results in null pointer dereference. The attack can be launched remotely. The pull request to fix this issue awaits acceptance.
When was CVE-2026-17500 disclosed?
CVE-2026-17500 was first published in the National Vulnerability Database on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-17500?
CVE-2026-17500 has a CVSS v3 base score of 5.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-17500?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17500, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17500
Is Your Infrastructure Affected by CVE-2026-17500?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.