dbcve.org
TensorrtApplication · Nvidia

CVE-2026-24188

HIGH · 7.5 CVSS v3.1 Published 2026-05-20
Fix available
A fix is available. Upgrade to 10.16.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
NVIDIA TensorRT contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to data tampering.

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 confidence

NVIDIA TensorRT contains an out-of-bounds write vulnerability that could allow an attacker to write data beyond allocated memory boundaries. Successful exploitation may lead to data tampering and potential code execution. The CVSS 7.5 score indicates high severity due to the potential for confidentiality and integrity impact.

MitigationApply NVIDIA's official TensorRT security patches when available. Identify all deployments using vulnerable TensorRT versions and update them accordingly. If patches are unavailable, restrict network access to TensorRT services and implement input validation as a temporary mitigation.

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
TensorrtApplication
Affected:< 10.16.1

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify TensorRT installation
    Run 'pip show tensorrt' or check for TensorRT libraries in /usr/local/tensorrt or /usr/lib/x86_64-linux-gnu/
    Affected if TensorRT is not installed - the system is not affected. If installed, proceed to version check.
  2. Check installed TensorRT version
    Run 'pip show tensorrt | grep Version' or use 'nvcc --version' to check CUDA/TensorRT version, or inspect the version file in the TensorRT installation directory
    Affected if Version is less than 10.16.1 - the installed version is vulnerable to CVE-2026-24188
  3. Confirm inference engine usage
    Review application code and runtime logs to determine if TensorRT inference engine (tensorrt.IExecutionContext or equivalent) is being used for model inference
    Affected if The inference engine component is actively used - this is the specific component containing the out-of-bounds write vulnerability
  4. Assess interface exposure
    Check network configuration, API endpoints, and service bindings to determine if TensorRT interfaces are accessible to untrusted users or network segments
    Affected if TensorRT interfaces are exposed to untrusted parties - combined with a vulnerable version, this increases exploitation risk

A system is affected if TensorRT is installed with a version below 10.16.1 and the inference engine component is in use, particularly if TensorRT interfaces are accessible to untrusted parties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 10.16.1 or later
Fixed in 10.16.1
Interim mitigation

Apply NVIDIA's official TensorRT security patches when available. Identify all deployments using vulnerable TensorRT versions and update them accordingly. If patches are unavailable, restrict network access to TensorRT services and implement input validation as a temporary mitigation.

Recommended fix High confidence

TensorRT 10.16.1 or later

  1. 1. Identify current TensorRT installation method (pip, apt, Docker container, or tar package)
  2. 2. For pip: Run 'pip install --upgrade tensorrt==10.16.1' or 'pip install --upgrade tensorrt>=10.16.1'
  3. 3. For apt: Run 'sudo apt-get update && sudo apt-get install tensorrt=10.16.1' (verify exact package name)
  4. 4. For Docker: Pull 'nvcr.io/nvidia/tensorrt:10.16.1-py3' or later tag
  5. 5. For tar package: Download TensorRT 10.16.1 from NVIDIA Developer website and follow installation guide
  6. 6. Verify installation by running 'python -c "import tensorrt; print(tensorrt.__version__)"' and confirm version is 10.16.1 or later
  7. 7. Test critical inference workflows to ensure functionality is maintained
Caveat Review NVIDIA TensorRT 10.16.1 release notes for any API changes or deprecations that may affect existing code

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tensorrt Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24188 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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