CVE-2026-24220
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-LLM for any platform contains a vulnerability in visual gen server, where an attacker could cause an unsafe deserialization by unauthorized zeroMQ deserialization. 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-LLM contains an unsafe deserialization vulnerability in its visual gen server component where unauthorized ZeroMQ deserialization can be exploited, potentially allowing remote code execution.
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
- Local
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/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.
-
Check if TensorRT-LLM is installedRun 'pip show tensorrt-llm' or 'nvidia-smi' and look for TensorRT-LLM package. Check installation directory typically at /usr/local/tensorrt-llm or via pip.Affected if TensorRT-LLM is installed and the visual gen server component is in use
-
Identify the visual gen server componentLook for process or service named 'visual_gen_server', 'visual-gen', or similar in running processes. Check /opt/nvidia/tensorrt-llm/visual_gen/ or installation paths for visual generation server files.Affected if Visual gen server component is running or installed
-
Verify ZeroMQ is in useCheck for open ports associated with ZeroMQ (typically ports 5555, 5556, 5570 or configurable). Run 'netstat -tlnp | grep -E "(5555|5556|5570)"' or check process list for zmq-related libraries.Affected if ZeroMQ ports are open or ZeroMQ libraries are loaded by the visual gen server
-
Check ZeroMQ configurationInspect config files in the visual gen server directory for ZeroMQ bind addresses. Look for 'zmq', 'zeromq', 'bind' settings in config.yaml, config.json, or similar files.Affected if ZeroMQ is configured to accept remote connections (0.0.0.0 rather than 127.0.0.1)
-
Review network exposureCheck firewall rules and network binding configuration. Verify if the visual gen server ZeroMQ ports are exposed to untrusted networks.Affected if ZeroMQ ports are accessible from untrusted network segments or internet-facing interfaces
You are affected if TensorRT-LLM with the visual gen server is installed, running, and has ZeroMQ ports exposed to untrusted access, allowing remote attackers to send malicious serialized payloads.
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 dataApply NVIDIA's patch when available; until then, restrict network access to the visual gen server and disable or firewall ZeroMQ ports if possible.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24220 — 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-24220 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