CVE-2026-24229
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 Linux contains a vulnerability in the disaggregated orchestrator component, where an attacker could read, write, or delete internal cluster state by sending requests to the FastAPI server. A successful exploit of this vulnerability might lead to information disclosure, data tampering, and denial of service.
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 for Linux contains a vulnerability in the disaggregated orchestrator's FastAPI server where an attacker can read, write, or delete internal cluster state without proper authorization. This likely stems from missing or insufficient access controls on the orchestrator API endpoints, enabling unauthorized CRUD operations on cluster metadata and state.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
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.
-
Identify installed TensorRT-LLM versionRun `pip show tensorrt-llm` or check the installed package version via your package manager. Compare against any known affected version ranges provided by NVIDIA.Affected if The installed version falls within an affected version range.
-
Verify disaggregated orchestrator is configuredLook for configuration files or environment variables that enable the disaggregated orchestrator feature in your TensorRT-LLM deployment (e.g., check for 'disaggregated' or 'orchestrator' in config files or startup scripts).Affected if The disaggregated orchestrator is enabled or configured in the environment.
-
Confirm FastAPI orchestrator server is runningCheck for running processes or listening ports associated with the TensorRT-LLM orchestrator FastAPI server (e.g., using `ps aux` or `netstat`/`ss` to identify the service).Affected if The FastAPI server for the disaggregated orchestrator is actively running.
-
Inspect access control configuration on orchestrator endpointsReview the orchestrator's FastAPI application code or configuration for authentication/authorization decorators (e.g., dependencies like `require_auth`, role checks, or middleware) on API route handlers.Affected if Authentication and role-based authorization are missing or insufficient on the API endpoints.
Your environment is affected if TensorRT-LLM with the disaggregated orchestrator FastAPI server is running and lacks proper access controls on its API endpoints.
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 dataImplement proper authentication and role-based authorization on all FastAPI endpoints in the disaggregated orchestrator, and restrict network access to the orchestrator server to trusted clients only.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24229 — 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-24229 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