NVIDIA NeMo Agent Toolkit: missing authentication rated CVSS 10.0

01What happened

NVIDIA published security bulletin 5912 for the NeMo Agent Toolkit on October 27, 2026, disclosing two separate flaws. Colin McDonough of 50words.com reported both, and YJK of ZUSO ART, working with the TrendAI Zero Day Initiative, is credited on the critical one. The toolkit is NVIDIA's open-source library for connecting teams of AI agents.

02How it works

Missing authentication for a critical function, classified CWE-306, is the mechanism behind CVE-2026-65145. NVIDIA's CVSS 3.1 vector, AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, describes a network-reachable flaw that needs no privileges and no user interaction, and that changes scope beyond the vulnerable component. NVIDIA states exploitation might lead to code execution, escalation of privileges, data tampering, denial of service and information disclosure, and publishes no further technical detail.

03Who is affected

NeMo Agent Toolkit versions 1.0 through 1.8.0 carry CVE-2026-65145, on all platforms. The separate SQL injection, CVE-2026-65151, affects a narrower range, versions 1.4 to 1.6. Deployments already on 1.9.0, released September 10, 2026, are past the fixed version for both.

04What to do

Update the NeMo Agent Toolkit to version 1.9.0 or later from the NVIDIA GitHub repository, which is NVIDIA's recommended action for both CVEs. Check running agent deployments for their installed toolkit version, because 1.9.0 shipped on September 10, 2026, several weeks before this disclosure.

Questions people ask

Which NeMo Agent Toolkit versions are affected by CVE-2026-65145?

NeMo Agent Toolkit versions 1.0 through 1.8.0 are affected by CVE-2026-65145 on all platforms, according to NVIDIA's bulletin. NVIDIA fixed the flaw in version 1.9.0. The second issue disclosed the same day, CVE-2026-65151, covers a narrower range of versions 1.4 to 1.6 and was fixed earlier, in release 1.7.0.

How do I fix CVE-2026-65145 in the NeMo Agent Toolkit?

Updating to NeMo Agent Toolkit 1.9.0 or later from the NVIDIA GitHub repository is the action NVIDIA recommends, and that release also covers the SQL injection flaw. Version 1.9.0 shipped on September 10, 2026, so operators who have updated since then are already covered, while anyone pinned to 1.8.0 or earlier remains exposed.

Why is CVE-2026-65145 scored CVSS 10.0?

NVIDIA's CVSS 3.1 vector for CVE-2026-65145 combines network reach, low attack complexity, no required privileges and no user interaction with high confidentiality, integrity and availability impact, plus a scope change. A scope change means the damage can extend past the vulnerable component, which pushes the base score to the 10.0 maximum.

Did NVIDIA say how CVE-2026-65145 can be exploited?

NVIDIA's bulletin describes CVE-2026-65145 only as a missing authentication issue, classified CWE-306, and lists the possible impacts: code execution, escalation of privileges, data tampering, denial of service and information disclosure. NVIDIA publishes no proof of concept, no affected endpoint and no exploitation details, so the version ranges and the CVSS vector are the facts defenders have.

Sources 4 links, all fetched

1. 1github.comNVIDIA Bulletin 5912
2. 2github.comCritical CVE Advisory
3. 3github.comSQL Injection Advisory
4. 4github.comToolkit 1.9.0 Release