CVE-2026-24189
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 · uneditedNVIDIA 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.
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 confidenceNVIDIA CUDA-Q has an endpoint vulnerability where unauthenticated attackers can send maliciously crafted requests to trigger an out-of-bounds read, potentially causing denial of service and information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 CUDA-Q installation and versionRun 'cuda-q --version' or check installed packages via system package manager (e.g., 'dpkg -l | grep cuda-q' or 'rpm -qa | grep cuda-q') to determine if NVIDIA CUDA-Q is present and note the installed version number.Affected if CUDA-Q is installed and the version falls within the vulnerable version range (compare your installed version to the affected ranges provided by NVIDIA).
-
Identify running CUDA-Q API serviceCheck for processes related to CUDA-Q API server (e.g., look for 'cuda-q-api', 'qpu', or similar services running via 'ps aux | grep -i cuda' or 'systemctl list-units | grep -i qpu'). Also check listening network ports commonly used by CUDA-Q API endpoints.Affected if The CUDA-Q API service process is running and listening on a network interface.
-
Assess API endpoint network exposureUse 'netstat -tlnp' or 'ss -tlnp' to identify which network addresses and ports the CUDA-Q API service is bound to. Determine if it is accessible from external networks or only from localhost.Affected if The API endpoint is bound to a non-localhost address or is accessible from network segments beyond the local host, allowing unauthenticated remote attackers to reach it.
-
Confirm API endpoint availabilityAttempt to reach the CUDA-Q API endpoint (commonly at paths like '/api/' or '/qpu/' depending on configuration) using curl or similar tool: 'curl -k https://<host>:<port>/api/' or 'http://<host>:<port>/qpu/' to verify the endpoint responds.Affected if The API endpoint responds to requests without authentication, confirming it is active and reachable.
A user is affected if NVIDIA CUDA-Q is installed with a vulnerable version AND the API endpoint service is running and network-accessible to unauthenticated attackers.
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 dataImplement proper input validation and bounds checking on the affected endpoint to prevent out-of-bounds memory access. Restrict network access to the endpoint until a patch is applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24189 — 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-24189 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