CVE-2026-104853
Description
A flaw was found in Nx. During migration planning, the application reads migration file paths from package manifests without validating that they remain within the intended directory. An attacker supplying a malicious package dependency can exploit this path traversal issue using directory traversal sequences or absolute paths. This can allow an attacker to write or truncate arbitrary files outside the designated temporary directory, leading to unauthorized file modification.
Déclaration
This issue affects the nx migrate planning path. In Red Hat products where Nx appears in source manifests (including Grafana, Ansible Automation Platform UI components, and related offerings), Nx is used only as a build-time or development dependency, is not shipped for customer use, and nx migrate is not invoked as part of product operation. Customers running the delivered packages or images are not exposed to this vulnerability. The services-management-platform javascript-clients component already includes a fixed Nx version.
Mesure d'atténuation
Red Hat is not aware of any mitigation or workaround that addresses this vulnerability at this time. Customers are advised to apply the relevant security update once available.
Détails du score du système commun d'évaluation des vulnérabilités (CVSS)
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
Les mesures et les scores CVSS suivants sont préliminaires et sujets à révision.
Répartition des scores CVSS v3
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Score de base | 5.8 | N/A | N/A |
| Vecteur d'attaque | Local | N/A | N/A |
| Complexité de l'attaque | High | N/A | N/A |
| Privilèges requis | None | N/A | N/A |
| Interaction avec l'utilisateur | Required | N/A | N/A |
| Champ d'application | Unchanged | N/A | N/A |
| Confidentialité | Low | N/A | N/A |
| Impact sur l'intégrité | High | N/A | N/A |
| Impact sur la disponibilité | Low | N/A | N/A |
Vecteur
Red Hat: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:L
Explication du score CVSS v3 de Red Hat
AV:L - exploitation occurs during local nx migrate planning. AC:H - requires a hostile package (or packageGroup member) and bypass of the default nx@latest handoff (NX_USE_LOCAL / NX_MIGRATE_USE_LOCAL / NX_MIGRATE_CLI_VERSION / --run-id / temp-install fallback). PR:N - no elevated privileges. UI:R - victim must run nx migrate. S:U - impact on the local system. C:L/I:H/A:L - primary impact is attacker-controlled write or truncate outside the temp dir; confidentiality/availability are secondary.
Comprendre la Défaillance (CWE)
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity
Technical Impact: Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.
Confidentiality
Technical Impact: Read Files or Directories
The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Questions fréquemment posées
Not sure what something means? Check out our Security Glossary.
Vous souhaitez recevoir des notifications d'errata ? Signez ici.
