Skip to main content
VulnerabilityPublished

CVE-2026-24189: NVIDIA CUDA-Q · Out-of-bounds Read

Affects NVIDIA CUDA-QSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 0.14.0 soon.

Data as of 30 Oct 2026, 11:34 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.14.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade NVIDIA CUDA-Q to 0.14.0.

Affected software

ProductAffectedFixed in
NVIDIACUDA-QAffected
  • =All versions prior to 0.14.0
Fixed in–
npmcuda-qpkg:npm/cuda-qOther threatsAffected
  • <0.14.0
Fixed in
  • 0.14.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should consider restricting network access to the vulnerable endpoint and monitor for suspicious activity related to malformed requests targeting CUDA-Q. No official remediation or temporary fix is currently available.

Description

NVIDIA CUDA-Q contains a vulnerability in an endpoint, where an unauthenticated attacker could cause an out-of-bounds read by sending a maliciously crafted request. A successful exploit of this vulnerability might lead to denial of service and information disclosure.

References

Community reviews

Loading reviews…