Security Bulletin: NVIDIA TensorRT-LLM - May 2026

F-TRTLLM-DESER-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

NVIDIA/TensorRT-LLMReported fixNVIDIA/TensorRT-LLM

Security Bulletin: NVIDIA TensorRT-LLM - May 2026

fixed publicly (mapped to unsafe deserialization class)

details

Finding IDs: F-TRTLLM-DESER-001
Status: fixed publicly (mapped to unsafe deserialization class)
Reported via: NVIDIA security contact
Note: NVIDIA TensorRT-LLM May 2026 bulletin lists unsafe deserialization CVE-2025-33255 and CVE-2026-24163 as fixed for versions prior to v1.2, and recommends TensorRT-LLM v1.2.1. this is mapped to F-TRTLLM-DESER-001 if the private report corresponds to the unsafe deserialization class; public acknowledgement credits a different reporter, so this is tracked as reported-fix mapping rather than public CVE credit.

F-TRTLLM-DESER-001: Needs source detail. The bulletin-to-report mapping is conditional and cannot establish this exact finding's mechanism. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TRTLLM-DESER-001

Security area (1seal assessment): Unclassified. The public bulletin-to-finding mapping is conditional and the bulletin could not be retrieved during this review. Its general deserialization class is not enough to classify this exact report. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.