High Memory corruption

CVE-2026-24262 — Out-of-bounds Write in NVIDIA DGX Spark

NVIDIA DGX Spark contains a vulnerability in the system firmware, where a privileged attacker could be able to cause an out-of-bounds write. A successful exploit of this vulnerability may lead to code execution, escalation of privileges, denial of service, information disclosure, and data tampering.

Published Aug 25, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: nvidia

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

NVIDIA

DGX Spark and 1 more

CVSS base

8.2

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (NVIDIA DGX Spark, NVIDIA Dgx Spark Uefi).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
NVIDIA	DGX Spark	version 0 to 1.110.12	Vulnerable	CVE Program (cve.org) e CISA ADP
NVIDIA	Dgx Spark Uefi	< 1.110.13	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

High

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.2	CVSS 3.1	High	1.5	6.0	psirt@nvidia.com via NIST National Vulnerability Database
8.2	CVSS 3.1	High	—	—	nvidia via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H (score shown at the top: psirt@nvidia.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.

endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

2026
Affected products added · nvidia/dgx spark
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 8.2
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 25, 2026 · nvidia

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

3 on the record

nvd.nist.gov/vuln/detail/CVE-2026-24262
US Government Resource, NIST National Vulnerability Database
github.com/NVIDIA/product-security/tree/main/2026/5867
Product, NIST National Vulnerability Database
www.cve.org/CVERecord
Third Party Advisory, NIST National Vulnerability Database

Elsewhere on this site

NVIDIA
every CVE for this vendor

Memory corruption
same class

CWE-787
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-47626 Out-of-bounds Write in NVIDIA Dgx Spark Uefi Aug 25, 2026
Medium CVE-2026-47624 NVIDIA DGX Spark contains a vulnerability in UEFI where a Attacker may cause a/an… Aug 25, 2026
Medium CVE-2026-24225 Out-of-bounds Read in NVIDIA Dgx Spark Uefi Aug 25, 2026
High CVE-2026-24263 NULL Pointer Dereference in NVIDIA Dgx Spark Uefi Aug 25, 2026
High CVE-2026-24218 NVIDIA DGX OS contains a vulnerability in the factory provisioning process, where the… May 20, 2026
Low CVE-2025-33200 NVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware, where an attacker… Nov 25, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-24262 is "Out-of-bounds Write in NVIDIA DGX Spark", rated High. It affects DGX Spark (NVIDIA); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.2 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.