Skip to main content
Menu
CVEs

SqueezeLLM out-of-bounds write in CUDA matvec kernel

CVE-2026-133612EUVD-2026-131576GHSA-PH4G-4P92-6H22Published , updated

5.1MediumCNA
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Not reported

Summary

SqueezeLLM from SqueezeAILab has a weakness in its CUDA Matvec Kernel where manipulating the full_row_indices argument can cause an out-of-bounds write. An attacker can trigger this remotely over a network with low privileges, and a user must take some action for the attack to succeed.

Written by a model

Original description

A weakness has been identified in SqueezeAILab SqueezeLLM up to a5fd71f353bf569feb7b55737c1c1493e78e8f31. This vulnerability affects the function vecquant4matmul_spmv_hybrid_nuq_perchannel of the file quant_cuda_kernel.cu of the component CUDA Matvec Kernel. Executing a manipulation of the argument full_row_indices can lead to out-of-bounds write. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.

What to do

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-133612 (SqueezeAILab SqueezeLLM CUDA Matvec Kernel quant_cuda_kernel.cu vecquant4matmul_spmv_hybrid_nuq_perchannel out-of-bounds write), 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-133612 (entry last updated 2026-11-20):
Affected:
- SqueezeAILab SqueezeLLM: 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-133612 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133612 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://vuldb.com/vuln/441203
- https://vuldb.com/vuln/441203/cti
- https://vuldb.com/cve/CVE-2026-133612
- https://vuldb.com/submit/1050821
- https://github.com/SqueezeAILab/SqueezeLLM/
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-133612
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-133612"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

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

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 8

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133612
RecordNVD · CVE-2026-133612
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · SqueezeAILab/SqueezeLLM · Issue #77
Other links 5
AdvisoryVulDB · Advisory #441203
AdvisoryVulDB · Threat intelligence #441203
AdvisoryVulDB · CVE-2026-133612 record
AdvisoryVulDB · Submission #1050821
RepositoryGitHub · SqueezeAILab/SqueezeLLM · Repository

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