Skip to main content
Menu
CVEs

gguf-tools out-of-bounds read in GGUF parser

CVE-2026-133610Published , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

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

Original 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

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure10/25CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 8

No corrections so far. Something wrong on this page? Report an error.