CVE-2026-133610 json
antirez gguf-tools GGUF gguflib.c gguf_get_tensor out-of-bounds
published yesterday modified yesterday also EUVD-2026-131574
- cvss
- 5.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
A vulnerability was found in antirez gguf-tools up to fdfafbed766db0a1e9019b07994cd88f133d1aab. The impacted element is the function gguf_get_tensor of the file gguflib.c of the component GGUF Parser. The manipulation of the argument offset/alignment results in out-of-bounds read. The attack can be launched remotely. The pull request to fix this issue awaits acceptance.
Patch / fix
- github.com/antirez/gguf-tools#33 pull request
Is CVE-2026-133610 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X |
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L/E:X/RL:X/RC:C |
| CNA | 3.0 | 6.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L/E:X/RL:X/RC:C |
| CNA | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P/E:ND/RL:ND/RC:C |
Affected products
- antirez gguf-tools
Classification
References
-
github.com
/antirez/gguf-tools/pull/33
issue-tracking, patch
-
vuldb.com
/vuln/441163
vdb-entry, technical-description
-
vuldb.com
/vuln/441163/cti
signature, permissions-required
-
vuldb.com
/cve/CVE-2026-133610
third-party-advisory
-
vuldb.com
/submit/1050817
third-party-advisory
-
github.com
/antirez/gguf-tools/
product
Sources
- CVE List CVE-2026-133610
- NVD CVE-2026-133610
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.