CVE-2025-58410VulnerabilityPublished 17 Nov 2025

CVE-2025-58410: Imagination Technologies Graphics DDK · 4.18

Affects Imagination Technologies Graphics DDKSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

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:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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.

What to do

Affected software

Product	Affected	Fixed in
Imagination Technologies Graphics DDK	Affected =23.3 =25.2	Fixed in–

AI-suggested

1. Apply official patches from Imagination Technologies as soon as they are released to address the improper memory protection handling in the Graphics DDK. 2. Until patches are available, restrict access to GPU device interfaces to trusted users and processes only, using strict access control policies. 3. Implement runtime monitoring of GPU system calls and memory access patterns to detect anomalous behavior indicative of exploitation attempts. 4. Employ containerization or virtualization techniques to isolate GPU workloads, minimizing the impact of potential breaches. 5. Regularly audit and update GPU driver versions across all systems to ensure no legacy vulnerable versions remain in use. 6. Coordinate with hardware and software vendors to validate the integrity of GPU drivers and firmware. 7. For cloud environments, enforce strict tenant isolation and monitor GPU resource usage for unusual activity. 8. Educate system administrators and security teams about this vulnerability and the importance of GPU security hygiene. 9. Incorporate GPU driver vulnerability scanning into regular vulnerability management programs. 10. Consider network segmentation to limit exposure of systems running vulnerable GPU drivers.

Description

Software installed and run as a non-privileged user may conduct improper GPU system calls to gain write permissions to memory buffers exported as read-only. This is caused by improper handling of the memory protections for the buffer resource.

Impact

For European organizations, the exploitation of CVE-2025-58410 could lead to unauthorized modification of sensitive data held in GPU memory buffers, potentially compromising confidentiality without affecting system availability or integrity directly. Industries relying heavily on GPU acceleration—such as automotive (for autonomous driving simulations), aerospace, media production, and scientific research—may face increased risk due to the reliance on affected Imagination Technologies Graphics DDK versions. Confidential data processed or cached in GPU memory could be altered or leaked, leading to intellectual property theft or data breaches. Additionally, attackers might leverage this vulnerability as a foothold to escalate privileges or move laterally within networks, especially in environments where GPU resources are shared or exposed over the network. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing the threat landscape. This vulnerability could also impact cloud service providers in Europe offering GPU-accelerated services, potentially affecting multiple tenants if isolation is compromised. The absence of known exploits provides a window for proactive defense, but also means organizations must act swiftly to patch and monitor systems before attackers develop weaponized code.

CWE-280Improper Handling of Insufficient Permissions or Privileges (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Always check to see if you have successfully accessed a resource or system functionality, and use proper error handling if it is unsuccessful. Do this even when you are operating in a highly privileged mode, because errors or environmental conditions might still cause a failure.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

imaginationtech.com/gpu-driver-vulnerabilities/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 17:36 UTC

WeaknessesCWE-280

Technical details

References

Community reviews

Related threats