EUVD-2026-115877
GHSA-c7j2-58jq-2h2r
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malformed input asset
-
ExploitDeliver to local user for processing
-
ExecutionTrigger heap OOB read in Compressonator SDK parser
-
ImpactLeak adjacent heap memory or crash application
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an attacker-controlled input to be processed locally by software using the AMD Compressonator SDK; the UI:P metric indicates passive user interaction (a user must load or process the malicious asset). The exact file format or SDK API that triggers the out-of-bounds read is not described in the available sources. Limiting factors that reduce real-world risk: local attack vector only (no network reachability), dependence on a user processing attacker-supplied content, and bounded impact - low-confidentiality memory disclosure or an application crash (DoS), with no integrity impact and no scope change to other systems. |
| Impact | This is a medium-severity, local-access issue rather than a high-urgency emergency. The supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:P) and CWE-125 indicate exploitation is not remote and requires local processing of attacker-supplied input plus user interaction; impact is bounded (VC:L confidentiality, VA:H availability/crash, no integrity impact). The vuln.today decision label is 'this_month', which aligns with the CVSS score of 5.2 - a routine-priority patch, not an act_now/emergency item. No EPSS score, no CISA KEV listing, and no public PoC or exploit reference were provided, so there is no signal of active or imminent exploitation. Net: a real but modest issue - schedule it into this month's patch cycle; it is a genuine memory-safety defect but not a widespread-exploitation priority. Note one tension to verify: the description says 'attacker with local access' (which maps to AV:L, i.e. local attack vector) while the main realistic trigger is a victim processing a crafted file; the vendor rated PR:L whereas a crafted-file parsing bug is typically PR:N - verify the exact privilege prerequisite against AMD bulletin AMD-SB-6032. |
| Exploit ScenarioDerived | An attacker crafts a malformed input (e.g. a texture/image asset) that is then processed locally by an application or tool built on the AMD Compressonator SDK. During parsing, the SDK reads past the end of a heap allocation, leaking adjacent heap memory to the attacker-influenced output or crashing the application. No public exploit was identified at time of analysis, and the precise malformed-input trigger is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
A heap-based out-of-bounds read in the AMD Compressonator SDK allows an attacker who can get crafted content processed by software built on the SDK to read past the end of an allocated heap buffer, yielding limited memory disclosure or an application crash. The vendor rates it 5.2 on CVSS 4.0 with a local attack vector; our independent CVSS 3.1 assessment (AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H) agrees this is a medium-severity, local-access issue rather than a high-urgency emergency, because exploitation requires the attacker to already have local reach and depends on a user loading or processing the malicious asset. No public exploit code or confirmed active exploitation (CISA KEV) is associated with this CVE at time of analysis, and the priority label is this_month.
RemediationAI
No fixed version is identified in the available data, so the actionable step is to consult AMD security bulletin AMD-SB-6032 (https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6032.html) for the vendor's patched release and any stated workaround, then upgrade the SDK and rebuild affected downstream applications against it. The available sources do not describe a vendor workaround, so none can be recommended here. Exposure is bounded by the exploitation prerequisites: the attack is local and requires a user to load or process attacker-supplied content through software using the SDK, so limiting which externally sourced assets are opened in SDK-based tools, and who can place assets in the processing pipeline, reduces the window until a patched build is available; the trade-off is reduced workflow flexibility for untrusted content. No public exploit code has been identified, which lowers immediate priority relative to the this_month decision label, but the advisory should still be rechecked for a released fix.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-125, an out-of-bounds read, specifically on the heap: the SDK's parsing or compression routines can consume attacker-influenced input and then index beyond a heap allocation instead of validating the length or offset first, which produces at most a low-confidentiality memory leak (C:L) or a hard application failure (A:H) with no integrity impact and no scope change. The affected technology is AMD's Compressonator SDK, a developer library for texture and image compression used by applications and tools that ingest external asset files; the risk therefore propagates to downstream products built on the SDK rather than to a single end-user application. The attack vector is local (AV:L) and the vendor's vector assigns UI:P, meaning the attacker does not control when the read triggers - the user must open or process the crafted asset - while our assessment records UI:R for the same passive-interaction dependency. Note the two vectors disagree on privileges: the published CVSS 4.0 vector carries PR:L (some local privilege required) whereas our independent assessment scores PR:N; the available sources do not resolve this discrepancy, so authentication or privilege requirements should be treated as not fully confirmed. No CPE identifiers were supplied, so the exact affected version range cannot be enumerated from the input, and the specific file format or SDK API call that triggers the over-read is not described in the available sources.
Know when Amd gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
Crafted input parsed locally by a victim, so AV:L/UI:R and PR:N (no attacker account needed - vendor used PR:L); OOB read yields C:L and crash gives A:H.
Primary rating from Vendor (amd).
CVSS VectorVendor: amd
DescriptionCVE.org
A heap-based out-of-bounds (OOB) read vulnerability in the AMD Compressonator SDK could allow an attacker with local access to read out-of-bounds heap memory, potentially resulting in information disclosure or application crash.
Threat Intelligence Overview
NVD
CVE.org
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
On BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, and 12.
Local privilege escalation and information disclosure in the Linux kernel on AMD Zen2 CPUs allows low-privileged users t
An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
An exploitable code execution vulnerability exists in the Shader functionality of AMD Radeon DirectX 11 Driver atidxx64.
An exploitable memory corruption vulnerability exists in AMD atidxx64.dll 26.20.15019.19000 graphics driver. Rated criti
plays_service.exe in the plays.tv service before 1.27.7.0, as distributed in AMD driver-installation packages and Gaming
A flaw was found in the KVM's AMD code for supporting SVM nested virtualization. Rated high severity (CVSS 8.8), this vu
AMD ATI atillk64.sys 5.11.9.0 allows low-privileged users to interact directly with physical memory by calling one of se
An exploitable out-of-bounds read vulnerability exists in AMD ATIDXX64.DLL driver, version 26.20.13001.29010. Rated high
AMD fglrx-driver before 15.9 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),
AMD fglrx-driver before 15.7 allows local users to gain privileges via a symlink attack. Rated high severity (CVSS 7.8),
Exploit-DB