CVE Details
| CVE ID |
Severity |
Affected Package |
Installed Version |
Fixed Version |
Date Published |
Date of Scan |
| CVE-2026-53655 |
MEDIUM |
tar |
7.5.11 |
7.5.16 |
2026-06-22T16:16:38.593Z |
2026-06-23T10:18:18.804605139Z |
Affected Docker Images
| Image Name |
SHA |
public.ecr.aws/lambda/nodejs:latest |
public.ecr.aws/lambda/nodejs@sha256:893686cc8a6ea6ddb41b96d094c5da6a3be66808dda7156d95285b33055b7551 |
public.ecr.aws/lambda/nodejs:24 |
public.ecr.aws/lambda/nodejs@sha256:904f7a98db07d37b59bf7edd90ed97bbba1cb574fd86db462205c68cfc55486c |
public.ecr.aws/lambda/nodejs:22 |
public.ecr.aws/lambda/nodejs@sha256:893686cc8a6ea6ddb41b96d094c5da6a3be66808dda7156d95285b33055b7551 |
Description
node-tar is a full-featured Tar for Node.js. Prior to 7.5.16, tar (node-tar) applies a PAX extended header's size= record (and other PAX overrides) to the next header entry of any type, including intermediary metadata headers such as a GNU long-name (L) or long-link (K) entry. Per POSIX pax, a PAX extended header (x) describes the next file entry, not the intermediary extension headers that may sit between the x header and the file it annotates. Because node-tar lets the PAX size override the byte length of an intervening L/K/x header, an attacker can desynchronize node-tar's stream cursor relative to every other mainstream tar implementation (GNU tar, libarchive/bsdtar, Python tarfile, and the now-fixed tar-rs / astral-tokio-tar). The result is a tar parser interpretation differential (CWE-436): a single crafted archive yields a different set of members under node-tar than under the reference tar tools. An attacker can use this to hide a member from one parser while it is visible to another, which defeats security tooling whose scanner and extractor disagree on archive contents (e.g. a malware/secret scanner that lists entries with one library while a downstream step extracts with another) This vulnerability is fixed in 7.5.16.
Remediation Steps
- Update the affected package
tar from version 7.5.11 to 7.5.16.
About this issue
- This issue may not contain all the information about the CVE nor the images it affects.
- This issue will not be updated with new information and the list of affected images may have changed since the creation of this issue.
- For more, visit Lambda Watchdog.
- This issue was created automatically by Lambda Watchdog.
CVE Details
MEDIUMtar7.5.117.5.162026-06-22T16:16:38.593Z2026-06-23T10:18:18.804605139ZAffected Docker Images
public.ecr.aws/lambda/nodejs:latestpublic.ecr.aws/lambda/nodejs@sha256:893686cc8a6ea6ddb41b96d094c5da6a3be66808dda7156d95285b33055b7551public.ecr.aws/lambda/nodejs:24public.ecr.aws/lambda/nodejs@sha256:904f7a98db07d37b59bf7edd90ed97bbba1cb574fd86db462205c68cfc55486cpublic.ecr.aws/lambda/nodejs:22public.ecr.aws/lambda/nodejs@sha256:893686cc8a6ea6ddb41b96d094c5da6a3be66808dda7156d95285b33055b7551Description
Remediation Steps
tarfrom version7.5.11to7.5.16.About this issue