CVE-2025-23304
BaseFortify
Publication date: 2025-08-13
Last updated on: 2025-09-24
Assigner: NVIDIA Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| nvidia | nemo | to 2.3.2 (exc) |
| apple | macos | * |
| microsoft | windows | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-23304 is a vulnerability in the NVIDIA NeMo library's model loading component that allows an attacker to perform code injection by loading .nemo files with maliciously crafted metadata. This flaw can lead to remote code execution and data tampering. [2]
How can this vulnerability impact me? :
Exploiting this vulnerability can result in remote code execution, allowing an attacker to run arbitrary code on the affected system. It can also lead to data tampering, compromising the confidentiality, integrity, and availability of data. [2]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade the NVIDIA NeMo library to the latest version that addresses the issue. Avoid loading .nemo files from untrusted or unknown sources, as the vulnerability involves maliciously crafted metadata in these files that can lead to code injection. Evaluate your specific configurations and restrict local access to the NeMo library to trusted users only. [1, 2]