CVE-2026-22165
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 · uneditedA web page that contains unusual WebGPU content loaded into the GPU GLES render process and can trigger a write UAF crash in the GPU GLES user-space shared library. On certain platforms, when the process executing graphics workload has system privileges this could enable further exploits on the device.
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 confidenceA use-after-free vulnerability in the GPU GLES user-space shared library allows a malicious web page with specially crafted WebGPU content to trigger a write-after-free condition in the GPU render process. When the graphics workload executes with system privileges on certain platforms, this memory corruption can potentially be chained for privilege escalation attacks.
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<= 25.2= 25.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WebGPU is enabled in the browser or applicationInspect browser settings or application configuration for WebGPU API support. In browsers like Chrome, navigate to chrome://flags or check via JavaScript: navigator.gpu !== undefinedAffected if WebGPU is enabled and the browser/application uses Imaginationtech GPU rendering
-
Identify the installed Imaginationtech Ddk versionCheck the GPU driver or library files associated with Imaginationtech. Look for version information in the GPU driver package, system info utilities, or by inspecting the GLES library files directlyAffected if The Ddk version is <= 25.2 or exactly 25.3
-
Confirm the GPU process runs with elevated privilegesInspect the GPU process privileges using system process monitoring tools. On affected platforms, check whether the GPU render process executes with system or root-level privileges rather than user-level isolationAffected if The GPU process runs with system/root privileges, increasing exploitation severity
-
Locate the GPU GLES user-space shared librarySearch for Imaginationtech GLES library files (typically named something like libGLES or img_egl) within the system graphics driver directoriesAffected if The GLES library from Imaginationtech Ddk is present and actively in use
A user is affected if WebGPU is enabled AND the Imaginationtech Ddk version is <= 25.2 or exactly 25.3, with the GPU process running with elevated privileges increasing the severity of the vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataDisable WebGPU support in browsers until a patch is available, or restrict GPU process privileges on affected platforms. Apply vendor-supplied patches for the GPU GLES library when released.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22165 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22165 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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