NVIDIA Infrastructure Controller 2.0 Fixes Fourteen Flaws

P1 — VALIDATE AND UPDATEMedium to Critical · 4.1 / 5.0 / 5.9 / 6.5 / 6.6 / 6.7 / 7.5 / 8.0 / 8.2 / 8.3 / 8.8 / 9.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

NVIDIA bulletin 5879 fixes fourteen vulnerabilities in NVIDIA Infrastructure Controller for Linux. Versions 0 through 1.9 are affected; NVIDIA directs users to update the controller software to version 2.0 or later from its supported repository.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory Infrastructure Controller instances and their deployed release, update through NVIDIA's infra-controller repository, and verify the replacement software is actually running.

Open the authoritative advisory

Source check: 2026-10-02 UTC. This notice reflects the primary-source evidence described below, not a completed update or exploitation test. Recheck the advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeNVIDIA Infrastructure Controller for Linux versions 0 through 1.9
AdvisoryNVIDIA Security Bulletin 5879
CVEsCVE-2026-65112, CVE-2026-65113, CVE-2026-65114, CVE-2026-65115, CVE-2026-65117, CVE-2026-65118, CVE-2026-65121, CVE-2026-65124, CVE-2026-65125, CVE-2026-65126, CVE-2026-65127, CVE-2026-65128, CVE-2026-65129, CVE-2026-65130
Authoritative release date2026-09-22 (NVIDIA CSAF initial release; bulletin title still says August 2026)
Authority revision date2026-09-22, revision 1.0.0 Initial Release. Midnight is the source's date representation, not independently verified publication-time precision.
Affected versionsNVIDIA Infrastructure Controller for Linux versions 0 through 1.9.
Fixed versionNVIDIA Infrastructure Controller 2.0 or later
CVSS base score4.1 / 5.0 / 5.9 / 6.5 / 6.6 / 6.7 / 7.5 / 8.0 / 8.2 / 8.3 / 8.8 / 9.8 (CVSS v3.1)
CVSS severityMedium to Critical
Exploitation statusNVIDIA bulletin 5879 does not state that these flaws are being exploited. That is not confirmation that exploitation has not occurred.

What Changed

The group includes hard-coded credentials, missing or improper authentication, certificate validation, resource exhaustion and injection flaws. CVE-2026-65113 has the 9.8 unauthenticated network vector; other entries require privileges or adjacent-network access. Do not apply that worst-case prerequisite to every CVE or to unrelated NVIDIA products.

What To Validate Now

  1. Inventory. Locate Linux Infrastructure Controller instances, deployed builds, reachable interfaces, service accounts and managed-infrastructure owners.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: NVIDIA Infrastructure Controller for Linux versions 0 through 1.9. Do not infer applicability from product family or severity alone.
  3. Remediate. Update Infrastructure Controller to 2.0 or later following NVIDIA's supported repository and deployment procedure. A repository clone alone does not replace a running older instance.
  4. Validate. Record the deployed release or build identifier and verify expected controller authentication, managed-system connectivity and representative approved management operations. Test rollback without leaving an old controller exposed.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.