CVE-2026-59875 (MEDIUM): detected in Lambda Docker Images.
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by locating the Docker build definition for the affected Lambda Node.js images and checking where tar 7.5.15 is installed. Update the package to 7.5.17, rebuild the nodejs:22, nodejs:24, and latest images, and verify that the vulnerability scan no longer reports CVE-2026-59875.
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-59875 | MEDIUM |
tar |
7.5.15 |
7.5.17 |
2026-07-08T16:16:34.107Z |
2026-07-22T10:18:15.468343918Z |
Affected Docker Images
| Image Name | SHA |
|---|---|
public.ecr.aws/lambda/nodejs:latest |
public.ecr.aws/lambda/nodejs@sha256:eca040a64243f44373fae948c0c1e13563d924a0b4c1b6a3c18d598f288ebf3f |
public.ecr.aws/lambda/nodejs:24 |
public.ecr.aws/lambda/nodejs@sha256:eca040a64243f44373fae948c0c1e13563d924a0b4c1b6a3c18d598f288ebf3f |
public.ecr.aws/lambda/nodejs:22 |
public.ecr.aws/lambda/nodejs@sha256:7fb30f61a372768a2ee1c1af89340e2b3b69782bc1135b0101669ee1106d1d0c |
Description
node-tar is a tar archive manipulation library for Node.js. Prior to 7.5.17, node-tar does not strip NUL bytes from PAX path and linkpath records in src/pax.ts, allowing a crafted archive with values to reach fs.lstat or fs.open and terminate the process with an uncaught exception. This issue is fixed in version 7.5.17.
Remediation Steps
- Update the affected package
tarfrom version7.5.15to7.5.17.
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-lambda-base-images
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws/aws-lambda-base-images#680 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aws/aws-lambda-base-images#676 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aws/aws-lambda-base-images#674 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
aws/aws-lambda-base-images#643 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aws/aws-lambda-base-images#642 ·
All issues in aws/aws-lambda-base-images
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/openedx-authz#460 ·