CVE-2026-24238
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 TensorRT for contains a vulnerability where an attacker might cause an improper validation of array index. A successful exploit of this vulnerability might lead to code execution.
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 TensorRT contains an improper array index validation vulnerability that could allow an attacker to trigger out-of-bounds access, potentially leading to code execution. The vulnerability exists in the TensorRT runtime where input or internal array indices are not properly validated before use.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 11.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Identify installed TensorRT versionRun 'pip show tensorrt' or 'python -c "import tensorrt; print(tensorrt.__version__)"' to get the version numberAffected if Version is less than 11.0 (e.g., 10.x, 9.x, 8.x, etc.)
-
Check TensorRT library files directlyLocate libnvinfer*.so files via 'find /usr -name "libnvinfer*.so*" 2>/dev/null' and inspect the library name for version, or use 'dpkg -l | grep tensorrt' on Debian-based systemsAffected if Library version shown is less than 11.0
-
Verify if TensorRT runtime is actively usedCheck if any Python scripts or applications import and use tensorrt (e.g., 'import tensorrt as trt'), create builders, or run inferenceAffected if TensorRT runtime is imported and used for inference or model building
-
Identify if external/untrusted input reaches TensorRTReview application code that calls TensorRT inference, checking for direct passage of user-controlled shapes, indices, or data buffers to TensorRT operations (e.g., ICudaEngine::createExecutionContext with unchecked inputs)Affected if Untrusted or user-supplied data is passed directly to TensorRT operations without validation
-
Check for network-exposed TensorRT inference endpointsAudit running services via 'netstat -tlnp' or review application configuration for TensorRT serving endpoints accessible to network clientsAffected if TensorRT inference is exposed over network without input validation layers
You are affected if TensorRT version is below 11.0 AND your application passes untrusted or external input directly to TensorRT runtime operations without validating array indices or shapes first.
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 data11.0
Apply the NVIDIA TensorRT security update/patch when available. Until then, restrict access to TensorRT inference endpoints and validate all input shapes/dimensions before passing to TensorRT operations.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24238 — 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-24238 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