NVIDIA’s security bulletin identifies a missing authentication condition in NeMo Agent Toolkit versions 1.0 through 1.8.0, with 1.9.0 listed as the fix. The CVSS 10 score signals severe potential consequences, but the public notice does not publish the exact service endpoint, whether a vulnerable mode is enabled by default, or a reproducing request. Those…
Inspect the ClaimsCase · DiggingBeagle record
NeMo Agent Toolkit lacked authentication at a potentially executable network boundary
NVIDIA assigned CVE-2026-65145 to a missing authentication condition with potentially severe code-execution impact.
Scope
NVIDIA product bulletin; affected 1.0 to 1.8.0, fixed in 1.9.0. The precise exposed route and default reachability have not been disclosed.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- not established
- Evidence
- Grade C
- Remediation
- fixed reported
- AI role
- AGAINST AI
Basis and provenance
NVIDIA identifies missing authentication and a fixed version; no public reproducing request or confirmed production campaign was supplied. Impact remains unrated because the scoped record does not establish a calibrated severity-to-impact-band mapping.
Assessed Oct 31, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-C26-NEMO-MISSING-AUTH-1 · NVIDIA NeMo Agent Toolkit 2026 security bulletin 5912
At a glance
A CVSS 10 value describes potential severity under the assumed exposure model, not a demonstrated remote exploit against all users.
Read the implicationsSpecific endpoint, deployment defaults, and independent proof of remote execution are not in the public advisory. No confirmed active-exploitation campaign was provided.
Limits and uncertaintyFull account
NVIDIA’s security bulletin identifies a missing authentication condition in NeMo Agent Toolkit versions 1.0 through 1.8.0, with 1.9.0 listed as the fix. The CVSS 10 score signals severe potential consequences, but the public notice does not publish the exact service endpoint, whether a vulnerable mode is enabled by default, or a reproducing request. Those gaps are material because an unauthenticated network entry point must be reachable before the stated impact can occur.
The issue concerns the service authorization boundary around an AI-agent tool environment, not the model spontaneously deciding to run code. A useful follow-up is to diff the fixed authentication path and test network exposure in each supported deployment mode. Reporting an unauthenticated exploit as already used in the wild would go beyond this source.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
Timeline
- Oct 29, 2026disclosure
Public disclosure
Claims & evidence
CLM-C26-NEMO-MISSING-AUTH-1NVIDIA reports CVE-2026-65145 as a missing authentication condition in NeMo Agent Toolkit 1.0 through 1.8.0, fixed in 1.9.0.supported
Basis: reported finding
- supportsNVIDIA NeMo Agent Toolkit 2026 security bulletin 5912vendor statement
NVIDIA product-security bulletin 5912, CVE-2026-65145 description and affected versions
Implications
A CVSS 10 value describes potential severity under the assumed exposure model, not a demonstrated remote exploit against all users.
Controls and mitigations
- Upgrade versions 1.0 through 1.8.0 to version 1.9.0 or later and restrict service reachability until per-route authentication can be tested.
Unknowns and contradictions
- Specific endpoint, deployment defaults, and independent proof of remote execution are not in the public advisory.
- No confirmed active-exploitation campaign was provided.
Sources and citation
Material revision history
- Oct 31, 2026 · Canonical change recorded · new in release · revision 208