ALAS2023-2026-1464

References: CVE-2026-23745  CVE-2026-23950 
FAQs regarding Amazon Linux ALAS/CVE Severity

Issue Overview:

node-tar is a Tar for Node.js. The node-tar library (<= 7.5.2) fails to sanitize the linkpath of Link (hardlink) and SymbolicLink entries when preservePaths is false (the default secure behavior). This allows malicious archives to bypass the extraction root restriction, leading to Arbitrary File Overwrite via hardlinks and Symlink Poisoning via absolute symlink targets. This vulnerability is fixed in 7.5.3. (CVE-2026-23745)

node-tar,a Tar for Node.js, has a race condition vulnerability in versions up to and including 7.5.3. This is due to an incomplete handling of Unicode path collisions in the `path-reservations` system. On case-insensitive or normalization-insensitive filesystems (such as macOS APFS, In which it has been tested), the library fails to lock colliding paths (e.g., `ss` and `ss`), allowing them to be processed in parallel. This bypasses the library's internal concurrency safeguards and permits Symlink Poisoning attacks via race conditions. The library uses a `PathReservations` system to ensure that metadata checks and file operations for the same path are serialized. This prevents race conditions where one entry might clobber another concurrently. This is a Race Condition which enables Arbitrary File Overwrite. This vulnerability affects users and systems using node-tar on macOS (APFS/HFS+). Because of using `NFD` Unicode normalization (in which `ss` and `ss` are different), conflicting paths do not have their order properly preserved under filesystems that ignore Unicode normalization (e.g., APFS (in which `ss` causes an inode collision with `ss`)). This enables an attacker to circumvent internal parallelization locks (`PathReservations`) using conflicting filenames within a malicious tar archive. The patch in version 7.5.4 updates `path-reservations.js` to use a normalization form that matches the target filesystem's behavior (e.g., `NFKD`), followed by first `toLocaleLowerCase('en')` and then `toLocaleUpperCase('en')`. As a workaround, users who cannot upgrade promptly, and who are programmatically using `node-tar` to extract arbitrary tarball data should filter out all `SymbolicLink` entries (as npm does) to defend against arbitrary file writes via this file system entry name collision issue. (CVE-2026-23950)

Issue Correction:
Run dnf update nodejs20 --releasever 2023.10.20260302 or dnf update --advisory ALAS2023-2026-1464 --releasever 2023.10.20260302 to update your system.
More information on how to update your system can be found on this page: Amazon Linux 2023 documentation

New Packages:

aarch64:
    nodejs20-debuginfo-20.20.0-1.amzn2023.0.2.aarch64
    nodejs20-libs-debuginfo-20.20.0-1.amzn2023.0.2.aarch64
    nodejs20-full-i18n-20.20.0-1.amzn2023.0.2.aarch64
    v8-11.3-devel-11.3.244.8-1.20.20.0.1.amzn2023.0.2.aarch64
    nodejs20-20.20.0-1.amzn2023.0.2.aarch64
    nodejs20-libs-20.20.0-1.amzn2023.0.2.aarch64
    nodejs20-devel-20.20.0-1.amzn2023.0.2.aarch64
    nodejs20-npm-10.8.2-1.20.20.0.1.amzn2023.0.2.aarch64
    nodejs20-debugsource-20.20.0-1.amzn2023.0.2.aarch64

noarch:
    nodejs20-docs-20.20.0-1.amzn2023.0.2.noarch

src:
    nodejs20-20.20.0-1.amzn2023.0.2.src

x86_64:
    nodejs20-full-i18n-20.20.0-1.amzn2023.0.2.x86_64
    nodejs20-libs-20.20.0-1.amzn2023.0.2.x86_64
    nodejs20-libs-debuginfo-20.20.0-1.amzn2023.0.2.x86_64
    nodejs20-debuginfo-20.20.0-1.amzn2023.0.2.x86_64
    v8-11.3-devel-11.3.244.8-1.20.20.0.1.amzn2023.0.2.x86_64
    nodejs20-devel-20.20.0-1.amzn2023.0.2.x86_64
    nodejs20-20.20.0-1.amzn2023.0.2.x86_64
    nodejs20-npm-10.8.2-1.20.20.0.1.amzn2023.0.2.x86_64
    nodejs20-debugsource-20.20.0-1.amzn2023.0.2.x86_64