HIGH CVSS 7.5
Published: 2026-05-20

CVE-2025-33255

nvidia tensorrt_llm Security Advisory (CVE-2025-33255)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2025-33255?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2025-33255 impacting nvidia tensorrt_llm. Evaluated with CVSS Base Score of 7.5 (HIGH).

Original NVD Description

Source: NIST NVD
NVIDIA TRT-LLM for any platform contains a vulnerability in MPI server, where an attacker could cause an unsafe deserialization. A successful exploit of this vulnerability might lead to code execution, denial of service, data tampering, and information disclosure.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Local (AV:L)
Requires local system execution permissions
Attack Complexity
High (AC:H)
Depends on race conditions or environment
Privileges Required
High (PR:H)
Administrative credentials required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product nvidia / tensorrt_llm
Affected Versions *
Weakness Enumeration CWE-502

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2025-33255 impacting nvidia tensorrt_llm.

⚡ Nuclei Detection Template (YAML) cve-2025-33255.yaml
id: cve-2025-33255

info:
  name: nvidia tensorrt_llm - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2025-33255 affecting nvidia tensorrt_llm.
    Evaluation: NVIDIA TRT-LLM for any platform contains a vulnerability in MPI server, where an attacker could cause an unsafe deserialization. A successful exploit ...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2025-33255
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 7.5
    cve-id: CVE-2025-33255
    cwe-id: CWE-502
  tags: cve,cve-2025-33255,nvidia,tensorrt_llm,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "tensorrt_llm"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2025-33255.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2025-33255
# Target: nvidia tensorrt_llm | CVSS: 7.5 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2025-33255 (nvidia tensorrt_llm)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against nvidia tensorrt_llm scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2025-33255.sh
# Recommended Remediation & Patching Commands for CVE-2025-33255
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install tensorrt_llm 2>/dev/null || \
sudo dnf upgrade tensorrt_llm 2>/dev/null || \
sudo yum update tensorrt_llm

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i tensorrt_llm 2>/dev/null || rpm -qa | grep -i tensorrt_llm

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2025-33255 in nvidia tensorrt_llm?

Review vendor-specific security notices and update nvidia tensorrt_llm packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2025-33255?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2025-33255?

CVE-2025-33255 is classified with a CVSS 3.1 Base Score of 7.5 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
7.5
HIGH SEVERITY
CVE ID CVE-2025-33255
Weakness CWE-502
Vendor nvidia
Product tensorrt_llm
Published 2026-05-20
Vector CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H