7.5
CVE-2026-44028
- EPSS 0.01%
- Veröffentlicht 05.05.2026 01:16:06
- Zuletzt bearbeitet 09.05.2026 04:16:26
- Quelle cve@mitre.org
- CVE-Watchlists
- Unerledigt
An issue was discovered in Nix before 2.34.7 and Lix before 2.95.2. Unbounded recursion in the NAR (Nix Archive) parser could lead to a stack-to-heap overflow when the parser is run on a coroutine stack. The stack is allocated without a guard page, which means that a stack overflow could overwrite memory on the heap and could allow arbitrary code execution as the Nix daemon (run as root in multi-user installations) if ASLR hardening is bypassed. This can be exploited by all users able to connect to the daemon (e.g., in Nix, this is configurable via the allowed-users setting, defaulting to all users). The fixed versions are 2.34.7, 2.33.6, 2.32.8, 2.31.5, 2.30.5, 2.29.4, and 2.28.7 for Nix (introduced in 2.24.4); and 2.95.2, 2.94.2, and 2.93.4 for Lix (introduced in 2.93.0).
Daten sind bereitgestellt durch das CVE Programm von einer CVE Numbering Authority (CNA) (Unstrukturiert).
HerstellerNixOS
≫
Produkt
Nix
Default Statusunaffected
Version
2.24.4
Version <
2.28.7
Status
affected
Version
2.29.0
Version <
2.29.4
Status
affected
Version
2.30.0
Version <
2.30.5
Status
affected
Version
2.31.0
Version <
2.31.5
Status
affected
Version
2.32.0
Version <
2.32.8
Status
affected
Version
2.33.0
Version <
2.33.6
Status
affected
Version
2.34.0
Version <
2.34.7
Status
affected
HerstellerLix Project
≫
Produkt
Lix
Default Statusunaffected
Version
2.93.0
Version <
2.93.4
Status
affected
Version
2.94.0
Version <
2.94.2
Status
affected
Version
2.95.0
Version <
2.95.2
Status
affected
VulnDex Vulnerability Enrichment
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.01% | 0.003 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| cve@mitre.org | 7.5 | 1.1 | 5.8 |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
|
CWE-674 Uncontrolled Recursion
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.