Skip to main content
Menu
CVEs

tract out-of-bounds read in operand arity indexing

CVE-2026-133616Published , updated

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

Summary

sonos tract has an out-of-bounds read flaw in its Operand Arity Indexing component that lets an attacker read memory beyond its intended bounds. An attacker can reach it remotely over the network with low-privilege access, and a user must take an action to trigger it.

Written by a model

Original description

A vulnerability was found in sonos tract up to 0.23.4. The affected element is the function InferenceRulesOp::rules of the file onnx/src/ops/math/gemm.rs of the component Operand Arity Indexing. The manipulation of the argument inputs/outputs results in out-of-bounds read. The attack can be executed remotely. The exploit has been made public and could be used. Upgrading to version 0.23.5 is sufficient to fix this issue. The patch is identified as 44c6f4a7ef988a5bafe98c8bb465d8a253599395. It is recommended to upgrade the affected component.

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-133616 (sonos tract Operand Arity Indexing gemm.rs rules 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-133616 (entry last updated 2026-11-20):
Affected:
- sonos tract: versions 0.23.0, 0.23.1, 0.23.2, 0.23.3, 0.23.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133616 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133616 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/sonos/tract/pull/2411
- https://github.com/sonos/tract/commit/44c6f4a7ef988a5bafe98c8bb465d8a253599395
- https://github.com/sonos/tract/releases/tag/v0.23.5
- https://vuldb.com/vuln/441217
- https://vuldb.com/vuln/441217/cti
- https://vuldb.com/cve/CVE-2026-133616
- https://vuldb.com/submit/1050822
- https://github.com/sonos/tract/
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-133616
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-133616"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

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

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 11

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133616
RecordNVD · CVE-2026-133616
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · sonos/tract · Issue #2391
Other links 8
AdvisoryVulDB · Advisory #441217
AdvisoryVulDB · Threat intelligence #441217
AdvisoryVulDB · CVE-2026-133616 record
AdvisoryVulDB · Submission #1050822
PatchGitHub · sonos/tract · Pull request #2411
PatchGitHub · sonos/tract · Commit 44c6f4a7
PatchGitHub · sonos/tract · Release v0.23.5
RepositoryGitHub · sonos/tract · Repository

Questions about CVE-2026-133616

Is CVE-2026-133616 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133616?

tract: versions 0.23.0, 0.23.1, 0.23.2, 0.23.3, 0.23.4.

Source: cve.now feed data

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