Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-65113 – Hard-Coded Credentials Leading to Full System Compromise – NVIDIA Infrastructure Co

Be the first to know when new zero-days emerge:

Summary

CVE-2026-65113 is a critical vulnerability in NVIDIA Infrastructure Controller for Linux caused by the use of hard-coded credentials (CWE-798). An unauthenticated network attacker who knows or discovers the embedded credential can gain unauthorized access to the controller, potentially leading to privilege escalation, data tampering, denial of service, and disclosure of sensitive information. NVIDIA rates this issue as CRITICAL with a CVSS v3.1 base score of 9.8.

Technical details

  • Root cause: The affected NVIDIA Infrastructure Controller software contains one or more hard-coded (embedded) credentials within the product, as classified under CWE-798 (Use of Hard-coded Credentials).
  • Trigger conditions: No authentication or user interaction is required; an attacker only needs network reachability to an exposed instance of the vulnerable service.
  • Attack vector: Network (AV:N) with low attack complexity (AC:L) and no privileges required (PR:N), meaning the vulnerability can be exploited remotely without prior access to the system.
  • Impact: Successful exploitation can result in escalation of privileges, tampering with data, denial of service, and unauthorized disclosure of information — the CVSS vector reflects high impact to confidentiality, integrity, and availability (C:H/I:H/A:H).

Affected software

  • NVIDIA Infrastructure Controller for Linux — versions 0 through 1.9 (per NVIDIA’s official CVE record; all releases in this range are listed as affected, with the vendor’s default status for other versions listed as unaffected).

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Consult NVIDIA’s official security advisory (referenced below) for the specific patched release of Infrastructure Controller and upgrade to a fixed version as soon as it is available/confirmed by the vendor. At the time of publication, NVIDIA had not yet published the detailed advisory content for this CVE beyond the CVE record itself, so organizations should monitor the vendor’s advisory page for the patched build number.
  • If no patch is yet available or cannot be applied immediately:
    • Restrict network access to NVIDIA Infrastructure Controller management interfaces to trusted, segmented management networks only; do not expose the controller directly to the internet or untrusted networks.
    • Apply firewall/ACL rules limiting inbound connections to the controller’s service ports to known administrative hosts.
    • Monitor authentication and access logs on the controller for unexpected or anomalous access, particularly attempts using default or documented service accounts.
    • Where supported, rotate or disable any credentials that may be shared or embedded in deployment images, and rebuild affected instances from a patched image once available.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge