Skip to main content
VulnerabilityPublished Updated

CVE-2026-21732: Imagination Technologies Graphics DDK · Use of Out-of-range Pointer Offset

Affects Imagination Technologies Graphics DDKSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Imagination TechnologiesGraphics DDKAffected
  • =23.2 RTM
  • ≥ 24.1 RTM, ≤ 25.1 RTM
Fixed in–

AI-suggested

  1. Apply official patches or updates from Imagination Technologies as soon as they become available to address this vulnerability.
  2. Until patches are released, restrict the privileges of the GPU compiler process to the minimum necessary, avoiding system-level privileges where possible.
  3. Implement strict input validation and sandboxing for GPU shader code processing, especially for content originating from untrusted sources such as web browsers.
  4. Monitor GPU compiler process behavior for crashes or anomalies that may indicate exploitation attempts.
  5. Employ network-level filtering to block or inspect suspicious web traffic that could deliver malicious shader code.
  6. Educate developers and security teams about the risks of shader code injection and the importance of secure GPU driver configurations.
  7. For embedded and IoT devices, ensure secure firmware update mechanisms are in place to rapidly deploy fixes.
  8. Collaborate with vendors and security communities to share threat intelligence related to this vulnerability.

Description

A web page that contains unusual GPU shader code is loaded into the GPU compiler process and can trigger a write out-of-bounds write crash in the GPU shader compiler library. On certain platforms, when the compiler process has system privileges this could enable further exploits on the device. An edge case using a very large value in switch statements in GPU shader code can cause a segmentation fault in the GPU shader compiler due to an out-of-bounds write access.

References

Community reviews

Loading reviews…