VulnerabilityPublished 30 Oct 2026

CVE-2026-18629: A web page that contains unusual GPU shader code is loaded into the GPU compiler process and can lead

Source GCVE Database

Compare

Authoritative record:CVE-2026-18629· High

Not known to be exploited.

Data as of 30 Oct 2026, 04:32 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-29cf-2525-q9j7

What to do

Affected software

Product	Affected	Fixed in
Imagination TechnologiesGraphics DDK	Affected =23.2 RTM2 =24.2 RTM2 ≥ 25.1 RTM2, ≤ 25.3 RTM =26.1 RTM1	Fixed in–

AI-suggested

Until a fix is available, users should monitor vendor communications for updates. No specific mitigations are provided in the available data.

Description

CVE-2026-18629 is a vulnerability in a GPU compiler process triggered by loading a web page containing unusual GPU shader code. The flaw arises from integer overflow during arithmetic on shader-derived values, causing incorrect memory allocation size calculations. This can lead to memory allocation failure and, if not properly handled, a NULL pointer dereference causing the compiler process to crash. On some platforms where the compiler runs with system privileges, this crash could enable further exploits or system instability.

Impact

The primary impact is a denial of service via crashing the GPU compiler process. On platforms where the compiler runs with system privileges, this crash could potentially be leveraged for further exploits, increasing the risk beyond simple denial of service. No confirmed exploitation in the wild has been reported.

Summary

This vulnerability involves a GPU compiler process that loads shader code from web pages. Due to improper handling of integer overflow in arithmetic operations on shader program values, memory allocation sizes may be miscalculated. This can cause allocation failures and subsequent NULL pointer dereferences at controlled offsets, crashing the compiler process. When the compiler process has elevated privileges, such crashes may lead to further exploitation opportunities on affected devices.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 04:32 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats