CVE Intelligence
Medium Authentication

CVE-2026-24259 — Missing Authentication for Critical Function in NVIDIA Tensorrt Llm

NVIDIA TensorRT-LLM for Linux contains a vulnerability where an attacker could cause missing authentication for a critical function. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

Published Jul 14, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: nvidia

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
NVIDIA
Tensorrt Llm
CVSS base
6.4
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (NVIDIA Tensorrt Llm).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
NVIDIA Tensorrt Llm ≥ 0.0 and ≤ v1.3.0 rc12 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.4 CVSS 3.1 Medium 0.5 5.9 psirt@nvidia.com via NIST National Vulnerability Database
6.4 CVSS 3.1 Medium — — nvidia via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: psirt@nvidia.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-306 · Missing Authentication for Critical Function

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
endpoint telemetry (EDR)authentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · nvidia/tensorrt-llm
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 15, 2026
  • CVSS changed · 6.4
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Jul 14, 2026 · nvidia

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

Elsewhere on this site

NVIDIA
every CVE for this vendor
Authentication
same class
CWE-306
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-47475 NVIDIA TensorRT-LLM contains a vulnerability in the OpenAI-compatible inference API… Jul 14, 2026
  • CVE-2026-47470 Improper Input Validation in NVIDIA Tensorrt Llm Jul 14, 2026
  • CVE-2026-47471 Heap-based Buffer Overflow in NVIDIA Tensorrt Llm Jul 14, 2026
  • CVE-2026-47473 NVIDIA TensorRT-LLM contains a vulnerability where an attacker could cause a… Jul 14, 2026
  • CVE-2026-47472 Deserialization of Untrusted Data in NVIDIA Tensorrt Llm Jul 14, 2026
  • CVE-2026-24234 Server-Side Request Forgery (SSRF) in NVIDIA Tensorrt Llm Jul 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-24259 is "Missing Authentication for Critical Function in NVIDIA Tensorrt Llm", rated Medium. It affects Tensorrt Llm (NVIDIA); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.4 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.