AQLM out-of-bounds read in Triton kernel
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
A flaw in the Triton Kernel component of Vahe1994 AQLM lets an attacker read memory outside the intended bounds by manipulating the codes argument. The attack can be launched remotely by someone with low-privilege access, and it requires a user to take action.
Written by a model
Original description
A vulnerability was found in Vahe1994 AQLM up to e79a896ed6656fe4ed06193d42d004e7d0bbdbb2. The affected element is an unknown function of the file inference_kernels/triton_kernel.py of the component Triton Kernel. Performing a manipulation of the argument codes results in out-of-bounds read. It is possible to initiate the attack remotely. The exploit has been made public and could be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. 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-133499 (Vahe1994 AQLM Triton Kernel triton_kernel.py 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-133499 (entry last updated 2026-11-20):
Affected:
- Vahe1994 AQLM: 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-133499 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133499 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/440920
- https://vuldb.com/vuln/440920/cti
- https://vuldb.com/cve/CVE-2026-133499
- https://vuldb.com/submit/1050811
- https://github.com/Vahe1994/AQLM/
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-133499
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-133499"}.Affected versions
- Vahe1994 AQLMVersion range not reported
cve.now Index
- 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
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133499 |
| Record | NVD · CVE-2026-133499 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · Vahe1994/AQLM · Issue #191 |
| Other links 5 | |
| Advisory | VulDB · Advisory #440920 |
| Advisory | VulDB · Threat intelligence #440920 |
| Advisory | VulDB · CVE-2026-133499 record |
| Advisory | VulDB · Submission #1050811 |
| Repository | GitHub · Vahe1994/AQLM · Repository |
Related
- CVE-2026-77347Pozeiden: Out-of-bounds read/write (crash / memory corruption) on valid diagrams in grid-layout renderers
- CVE-2026-62321Netatalk: afpd Spotlight RPC heap-buffer-overflow in nested sl_pack_filemeta() marshalling
- CVE-2026-49388Netatalk: Heap out-of-bounds read in afpd Spotlight RPC unmarshalling via unbounded toc_index in sl_unpack_loop()
- CVE-2026-49387Netatalk: Heap out-of-bounds read in afpd Spotlight RPC unmarshalling via unbounded element count in sl_unpack_ints() and sibling handlers
- CVE-2026-45356Netatalk: Unsigned Integer Underflow in Spotlight RPC Count Decrement (sl_unpack_loop)
- CVE-2026-45355Netatalk: Integer Underflow in Spotlight RPC String Length Calculation (sl_unpack_cpx)
No corrections so far. Something wrong on this page? Report an error.