CVE-2026-73566 (HIGH): detected in Lambda Docker Images.

Open Beginner friendly
#674 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, node.js

Research direction

Start with the Docker image definitions and build process for the Lambda Node.js images listed in the issue, then check where the installed tar package version comes from. Update the affected package to 7.5.21, rebuild the listed images, and verify that the vulnerability scan no longer reports CVE-2026-73566.

Written by the indexing model from the issue text.

Description

CVE Details

CVE ID Severity Affected Package Installed Version Fixed Version Date Published Date of Scan
CVE-2026-73566 HIGH tar 7.5.16 7.5.21 2026-08-13T18:18:19.25Z 2026-08-22T10:18:29.036623362Z

Affected Docker Images

Image Name SHA
public.ecr.aws/lambda/nodejs:latest public.ecr.aws/lambda/nodejs@sha256:1ff82da6fcff5cb4d0518505aeba477acab4d5bc230e257ac3d0450a77fbc169
public.ecr.aws/lambda/nodejs:24 public.ecr.aws/lambda/nodejs@sha256:1ff82da6fcff5cb4d0518505aeba477acab4d5bc230e257ac3d0450a77fbc169
public.ecr.aws/lambda/nodejs:22 public.ecr.aws/lambda/nodejs@sha256:8e26dc1314af70609939e524f4474a3043a945bfe862779ef408deb2962ce945

Description

node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.21, node-tar's filesFilter in src/list.ts uses the recursive mapHas helper to walk an archive entry path upward with path.dirname() and no segment cap when tar.t(...) or tar.x(...) receives a non-empty member-selection list. A crafted GNU L or PAX x long-path header with thousands of slash-separated segments reaches this.filter(entry.path, entry) in Parser[CONSUMEHEADER] in src/parse.ts before Unpack[CHECKPATH] applies maxDepth, causing an uncatchable RangeError stack overflow that terminates asynchronous and streaming Node.js consumers. This issue is fixed in version 7.5.21.


Remediation Steps
  • Update the affected package tar from version 7.5.16 to 7.5.21.
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.
Dominant language
No language data
Stars
777
Forks
118
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-lambda-base-images

All issues in aws/aws-lambda-base-images

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.