slangpy out-of-bounds read in EXR image loader
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Summary
A flaw in the EXR Image Loader component of shader-slang slangpy allows an out-of-bounds read, which lets an attacker read data outside the intended memory range. The attack can be launched remotely and without logging in, but it requires a user to take an action first.
Written by a model
Original description
A flaw has been found in shader-slang slangpy up to 0.43.1. This vulnerability affects the function tinyexr::DecodePixelData in the library external/include/tinyexr.h of the component EXR Image Loader. Executing a manipulation can lead to out-of-bounds read. The attack may be performed from remote.
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-133621 (shader-slang slangpy EXR Image Loader tinyexr.h DecodePixelData 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-133621 (entry last updated 2026-11-20):
Affected:
- shader-slang slangpy: versions 0.43.0, 0.43.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133621 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133621 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/shader-slang/slangpy/pull/1239
- https://vuldb.com/vuln/441269
- https://vuldb.com/vuln/441269/cti
- https://vuldb.com/cve/CVE-2026-133621
- https://vuldb.com/submit/1050818
- https://github.com/shader-slang/slangpy/
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-133621
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-133621"}.Affected versions
- shader-slang slangpy0.43.0, 0.43.1
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · 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 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133621 |
| Record | NVD · CVE-2026-133621 |
| Other links 6 | |
| Advisory | VulDB · Advisory #441269 |
| Advisory | VulDB · Threat intelligence #441269 |
| Advisory | VulDB · CVE-2026-133621 record |
| Advisory | VulDB · Submission #1050818 |
| Patch | GitHub · shader-slang/slangpy · Pull request #1239 |
| Repository | GitHub · shader-slang/slangpy · Repository |
Questions about CVE-2026-133621
Is CVE-2026-133621 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-133621?
slangpy: versions 0.43.0, 0.43.1.
Source: cve.now feed data
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.