VulnerabilityPublished 4 Sep 2025

CVE-2025-23261: NVIDIA NVOS · Sensitive Data in Logs

Affects NVIDIA NVOSSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
NVIDIA NVOS	Affected =25.02.22 =25.02.23	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should first inventory all NVOS devices and verify if they run affected versions (25.02.21xx, 25.02.22xx, 25.02.23xx). Until patches are available, organizations should restrict local access to NVOS systems to trusted administrators only and implement strict access controls on log files to prevent unauthorized reading. Monitoring and auditing access to logs should be enhanced to detect any unusual access patterns. Organizations should also consider implementing additional encryption or secure logging mechanisms if supported by NVOS to protect sensitive information in logs. Password policies should enforce strong, complex passwords to reduce the risk of successful offline cracking of exposed hashes. Network segmentation can limit the exposure of NVOS devices and logs to only necessary personnel. Finally, organizations should stay alert for NVIDIA security advisories and apply patches promptly once released. If possible, disable or limit verbose logging of authentication events until the issue is resolved.

Description

NVIDIA Cumulus Linux and NVOS products contain a vulnerability, where hashed user passwords are not properly suppressed in log files, potentially disclosing information to unauthorized users.

Impact

For European organizations, the exposure of hashed user passwords in NVOS logs could lead to significant confidentiality breaches, especially in environments where NVOS is used to manage critical network infrastructure or data center operations. If an attacker gains local access to the system or can access log files through misconfigurations or insider threats, they could extract password hashes and attempt offline cracking. This could result in unauthorized access to administrative accounts or other privileged users, potentially enabling further compromise of network devices or services. Given the medium severity and local access requirement, the threat is more pronounced in organizations with less stringent internal access controls or where NVOS devices are deployed in sensitive environments. The lack of impact on integrity and availability means the vulnerability does not directly enable system manipulation or denial of service, but the confidentiality breach could facilitate subsequent attacks. European organizations with compliance obligations under GDPR must also consider the risk of exposing user credential data, which could lead to regulatory penalties if not properly managed.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Sep 2025, 15:58 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats