CVE-2025-52993

June 27, 2025, 2:15 p.m.

5.6
Medium

Description

A race condition in the Nix, Lix, and Guix package managers enables changing the ownership of arbitrary files to the UID and GID of the build user (e.g., nixbld* or guixbuild*). This affects Nix before 2.24.15, 2.26.4, 2.28.4, and 2.29.1; Lix before 2.91.2, 2.92.2, and 2.93.1; and Guix before 1.4.0-38.0e79d5b.

Product(s) Impacted

Vendor Product Versions
Nixos
  • Nix
  • <2.24.15, <2.26.4, <2.28.4, <2.29.1
Lix
  • Lix
  • <2.91.2, <2.92.2, <2.93.1
Guix
  • Guix
  • <1.4.0-38.0e79d5b

Weaknesses

Common security weaknesses mapped to this vulnerability.

CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.

*CPE(s)

Affected systems and software identified for this CVE.

Type Vendor Product Version Update Edition Language Software Edition Target Software Target Hardware Other Information
a nixos nix <2.24.15 / / / / / / /
a nixos nix <2.26.4 / / / / / / /
a nixos nix <2.28.4 / / / / / / /
a nixos nix <2.29.1 / / / / / / /
a lix lix <2.91.2 / / / / / / /
a lix lix <2.92.2 / / / / / / /
a lix lix <2.93.1 / / / / / / /
a guix guix <1.4.0-38.0e79d5b / / / / / / /

CVSS Score

5.6 / 10

CVSS Data - 3.1

  • Attack Vector: LOCAL
  • Attack Complexity: HIGH
  • Privileges Required: NONE
  • Scope: CHANGED
  • Confidentiality Impact: LOW
  • Integrity Impact: LOW
  • Availability Impact: LOW
  • CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

    View Vector String

Timeline

Published: June 27, 2025, 2:15 p.m.
Last Modified: June 27, 2025, 2:15 p.m.

Status : Received

CVE has been recently published to the CVE List and has been received by the NVD.

More info

Source

cve@mitre.org

*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.