Infrastructure Controller: Use of Hard-coded Password
CVE-2026-65117 is a high-severity use of hard-coded password vulnerability in Infrastructure Controller from NVIDIA, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected Infrastructure Controller versions: 0 to 1.9. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Infra Controller to 2.0.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | Infrastructure Controller | 0 to 1.9 | Not stated |
| NVIDIA | Infra Controller | before 2.0.0 | 2.0.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.0 | Medium | CNA (nvidia.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
NVIDIA Infrastructure Controller for Linux contains a vulnerability where an attacker could cause use of a hard-coded password. A successful exploit of this vulnerability might lead to data tampering, denial of service, and information disclosure.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Hard-coded Password
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound authentication to external components.
How developers prevent this class of flaw
- For outbound authentication: store passwords outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible.
- For inbound authentication: Rather than hard-code a default username and password for first time logins, utilize a first login mode that requires the user to enter a unique strong password.
- Perform access control checks and limit which entities can access the feature that requires the hard-coded password. For example, a feature might only be enabled through the system console instead of through a network connection.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- nvd.nist.gov/vuln/detail/CVE-2026-65117US Government Resource
- cve.org/CVERecord?id=CVE-2026-65117Third Party Advisory
Other vulnerabilities in Infrastructure Controller
- 9.8 Critical severity
- 8.3 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.1 High severity
Recent Use of Hard-coded Password vulnerabilities
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
Spotted an error? Tell us.