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

The authority published NVIDIA Security Bulletin 5879 for NVIDIA Infrastructure Controller for Linux versions 0 through 1.9. NVIDIA released version 2.0 to address authentication, credential, injection, certificate-validation, resource-consumption, path, workflow, and information-disclosure weaknesses. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory NVIDIA Infrastructure Controller for Linux versions 0 through 1.9, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-09-22 UTC. Recheck the authoritative 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 00:00:00 UTC
Authority revision date2026-09-22 00:00:00 UTC
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 statusNot stated by the authority; no exploitation claim is inferred.

What Changed

NVIDIA released version 2.0 to address authentication, credential, injection, certificate-validation, resource-consumption, path, workflow, and information-disclosure weaknesses.

What To Validate Now

  1. Inventory. Locate NVIDIA Infrastructure Controller for Linux versions 0 through 1.9 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  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. Apply NVIDIA Infrastructure Controller 2.0 or later through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  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.