dbcve.org
DdkApplication · Imaginationtech

CVE-2026-21734

HIGH · 7.7 CVSS v3.1 Published 2026-06-26
Fix available
A fix is available. Upgrade to after 25.2 or later.
See remediation →
82/100
Remediation priority · High
No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 small value in GPU shader code can cause a segmentation fault in the GPU shader compiler due to am out-of-bounds write.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A memory corruption vulnerability exists in the GPU shader compiler where malformed shader code containing an unusually small value triggers an out-of-bounds write, causing a segmentation fault. When the GPU compiler process runs with system privileges on certain platforms, this condition could potentially be leveraged for privilege escalation attacks.

MitigationImplement bounds checking and input validation in the GPU shader compiler to prevent out-of-bounds memory writes when processing unusual or edge-case shader values. Consider running the compiler process with reduced privileges to limit escalation potential.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DdkApplication
Affected:<= 25.2= 25.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Imaginationtech Ddk installation and version
    Locate the Imaginationtech Ddk software installation directory and retrieve the installed version number, typically found in version metadata files, package information, or product-specific configuration files
    Affected if The installed version is 25.3 or any version <= 25.2
  2. Confirm GPU shader compiler is active
    Verify that the GPU shader compiler component is loaded and actively processing shader code in the environment, typically through process listing or service status checks
    Affected if The GPU shader compiler is running and processing shader input
  3. Check shader compilation workflow
    Inspect the shader compilation pipeline to confirm malformed or unusual shader code can be submitted for processing
    Affected if Unusual or edge-case shader values can reach the compiler without validation
  4. Verify compiler process privileges
    Examine the user context and privilege level under which the GPU compiler process executes
    Affected if The compiler process runs with elevated or system-level privileges

A system is affected if it runs Imaginationtech Ddk version 25.3 or <= 25.2 with the GPU shader compiler enabled processing potentially malformed shader code, especially if the compiler runs with elevated privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 25.2
Interim mitigation

Implement bounds checking and input validation in the GPU shader compiler to prevent out-of-bounds memory writes when processing unusual or edge-case shader values. Consider running the compiler process with reduced privileges to limit escalation potential.

Recommended fix Moderate confidence

Ddk version 25.4 or later (verify with Imagination Technologies)

  1. 1. Identify the current Ddk version installed in your environment by checking the GPU driver or compiler library version.
  2. 2. Contact Imagination Technologies or check their official support channels to obtain the fixed release (version 25.4 or later).
  3. 3. Download the updated Ddk package from a trusted Imagination Technologies source.
  4. 4. Follow the vendor's documented upgrade procedure to replace the affected GPU shader compiler library.
  5. 5. Verify the new version is correctly installed and test that GPU shader compilation functions normally.
  6. 6. Test that the previously vulnerable code path (loading web pages with unusual GPU shader code) no longer triggers the out-of-bounds write.
Caveat Check release notes for any API changes or driver compatibility impacts before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ddk Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21734 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data