Resiliency Extension: UNIX Symbolic Link (Symlink) Following
CVE-2025-33225 is a high-severity UNIX symbolic link (symlink) following vulnerability in Resiliency Extension from NVIDIA, with a CVSS 3.1 base score of 8.4 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. Affected Resiliency Extension versions: Main branch prior to 0.5.0 release. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.3% 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 Nvidia Resiliency Extension to 0.5.0 or a later version.
- Read the advisory on nvidia.custhelp.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | Resiliency Extension | Main branch prior to 0.5.0 release | Not stated |
| NVIDIA | Nvidia Resiliency Extension | before 0.5.0; 0.5.0 | 0.5.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
- LocalThe attacker needs local access or must trick a user into running something.
- 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:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (nvidia.com).
Official description
NVIDIA Resiliency Extension for Linux contains a vulnerability in log aggregation, where an attacker could cause predictable log-file names. A successful exploit of this vulnerability may lead to escalation of privileges, code execution, denial of service, information disclosure, and data tampering.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: UNIX Symbolic Link (Symlink) Following
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
How developers prevent this class of flaw
- Symbolic link attacks often occur when a program creates a tmp directory that stores files/links. Access to the directory should be restricted to the program as to prevent attackers from manipulating the files.
- Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.
More UNIX Symbolic Link (Symlink) Following vulnerabilities (CWE-61)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- nvd.nist.gov/vuln/detail/CVE-2025-33225US Government Resource, VDB Entry
- cve.org/CVERecord?id=CVE-2025-33225Third Party Advisory
Other vulnerabilities in Resiliency Extension
- 7.0 High severity
Recent UNIX Symbolic Link (Symlink) Following vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 10.0 Critical severity
- 10.0 Critical severity
Spotted an error? Tell us.