Friday, October 16, 2026
Follow on LinkedIn

NVIDIA Fixes Linux Component Flaws That Could Expose Sensitive System Information

NVIDIA released a security update for its Infrastructure Controller software for Linux, addressing 14 vulnerabilities that could let attackers access sensitive system information, execute code, alter data, or disrupt affected environments.

The update, published in NVIDIA’s September 2026 Infrastructure Controller security bulletin, affects versions 0 through 1.9. NVIDIA recommends that organizations clone or update the software to version 2.0 or later to address all reported issues.

Among the patched flaws is CVE-2026-65127, a medium-severity vulnerability caused by uncleared debug information. The issue carries a CVSS score of 4.1 and is tracked as CWE-1258.

An attacker with local access, high privileges, and favorable conditions could potentially retrieve sensitive system information left exposed through debugging artifacts.

While the debug-information issue requires significant attacker access, it is part of a broader security update containing several more serious vulnerabilities.

NVIDIA Fixes Linux Component Flaws

The most critical flaw, CVE-2026-65113, received a CVSS score of 9.8. NVIDIA said the issue involves hard-coded credentials in Infrastructure Controller for Linux.

A remote, unauthenticated attacker could potentially exploit the vulnerability to gain elevated privileges, manipulate data, cause a denial-of-service condition, or disclose information.

NVIDIA also fixed CVE-2026-65128, an SQL injection vulnerability with a CVSS score of 8.8. Successful exploitation may allow code execution, data manipulation, service disruption, and information disclosure. The flaw requires low privileges but no user interaction.

Other high-severity issues include missing or improper authentication weaknesses, OS command injection, and improper certificate validation.

CVE IDVulnerabilityCVSS v3.1SeverityCWE
CVE-2026-65113Use of hard-coded credentials9.8CriticalCWE-798
CVE-2026-65128SQL injection8.8HighCWE-89
CVE-2026-65114Missing authentication for critical function8.3HighCWE-306
CVE-2026-65121Improper authentication8.2HighCWE-287
CVE-2026-65130OS command injection8.0HighCWE-78
CVE-2026-65118Improper certificate validation7.5HighCWE-295
CVE-2026-65129Improper certificate validation6.7MediumCWE-295
CVE-2026-65125External control of file name or path6.6MediumCWE-73
CVE-2026-65115Uncontrolled resource consumption6.5MediumCWE-400
CVE-2026-65112Uncontrolled resource consumption6.5MediumCWE-400
CVE-2026-65124XML injection5.9MediumCWE-91
CVE-2026-65126Improper enforcement of behavioral workflow5.0MediumCWE-841
CVE-2026-65117Use of hard-coded password5.0MediumCWE-259
CVE-2026-65127Exposure of sensitive system information through uncleared debug information4.1MediumCWE-1258

CVE-2026-65114, rated 8.3, could allow data tampering, denial of service, and information disclosure because a critical function lacked proper authentication. CVE-2026-65121, rated 8.2, could permit privilege escalation and data exposure through improper authentication.

The update also resolves CVE-2026-65130, an OS command injection issue with a CVSS score of 8.0. Although exploitation requires high privileges and a high attack complexity, a successful attack could lead to code execution and a complete compromise of confidentiality, integrity, and availability.

Additional fixes address two uncontrolled resource consumption vulnerabilities, CVE-2026-65115 and CVE-2026-65112, both rated 6.5. An authenticated attacker could exploit these issues to cause denial-of-service conditions.

NVIDIA also remediated external control of file paths, XML injection, hard-coded password use, certificate-validation issues, and improper workflow enforcement.

Infrastructure Controller deployments may be used in environments that manage NVIDIA infrastructure components, making timely remediation important.

Organizations should identify systems running Infrastructure Controller versions 0 through 1.9, update them to version 2.0 or later, and review exposed services, access controls, credentials, logs, and network segmentation.

NVIDIA noted that its severity ratings reflect average risk across varied deployments and may not represent the risk to every local installation. Security teams should evaluate exposure based on their configurations, user privileges, network accessibility, and the affected controller’s operational role.

Cut every SOC alert investigation by 21 min. Power your SOC with instant IOC context for immediate response: Integrate TI Lookup in your SOC

Abinaya
Abinayahttps://cybersecuritynews.com/
Abi is a Security Editor and fellow reporter with Cyber Security News. She is covering various cyber security incidents happening in the Cyber Space.
0-Hour Cyber Security Alerts!
Get the latest Cyber security News sent directly to your inbox.

Cyber Security Guide

Latest Cyber News

Expert Talks