merge queue: queuing main (bee743a) and [#2278 + #2279] together

[mergify]

🎉 This combination of pull requests has been checked successfully and will be merged soon. 🎉

Branch main (bee743a) and [#2278 + #2279] are queued together for merge.

This pull request has been created by Mergify to check the mergeability of [#2278 + #2279].
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule Github Actions Updates for merge:

• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

• author = renovate[bot]
  • Update github/gh-aw-actions action to v0.80.6 #2278
  • Update softprops/action-gh-release action to v3.0.1 #2279
• any of:
  • files ~= ^.github/workflows
    • Update github/gh-aw-actions action to v0.80.6 #2278
    • Update softprops/action-gh-release action to v3.0.1 #2279
  • files ~= action.yaml$
    • Update github/gh-aw-actions action to v0.80.6 #2278
    • Update softprops/action-gh-release action to v3.0.1 #2279
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
    • Update github/gh-aw-actions action to v0.80.6 #2278
    • Update softprops/action-gh-release action to v3.0.1 #2279
  • check-skipped = Mergify Merge Protections
    • Update github/gh-aw-actions action to v0.80.6 #2278
    • Update softprops/action-gh-release action to v3.0.1 #2279
  • check-success = Mergify Merge Protections
    • Update github/gh-aw-actions action to v0.80.6 #2278
    • Update softprops/action-gh-release action to v3.0.1 #2279

---
checking_base_sha: bee743a82640d868e6358b08874153fc97633756
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 2278
    scopes: []
  - number: 2279
    scopes: []
scopes: []
...

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.github/workflows/agentics-maintenance.yml	19% smaller
.github/workflows/ci_tools.yaml	18% smaller
.github/workflows/daily-malicious-code-scan.lock.yml	18% smaller
.github/workflows/agents-md-maintenance.lock.yml	18% smaller
.github/workflows/ci-coach.lock.yml	18% smaller
.github/workflows/code-simplifier.lock.yml	18% smaller
.github/workflows/ci-doctor.lock.yml	18% smaller
.github/workflows/build.yaml	17% smaller

[sourcery-ai]

Reviewer's Guide

Updates pinned GitHub Actions versions across multiple workflow and lock files, primarily bumping github/gh-aw-actions setup/setup-cli to v0.80.6 and softprops/action-gh-release to v3.0.1 to keep CI tooling current and consistent.

File-Level Changes

Change	Details	Files
Bump github/gh-aw-actions setup and setup-cli actions from v0.80.4 to v0.80.6 across CI workflow and lock files.	Update pinned commit for github/gh-aw-actions/setup from 00c24a5 (v0.80.4) to c20f9e7 (v0.80.6) in all affected jobs. Update pinned commit for github/gh-aw-actions/setup-cli from 00c24a5 (v0.80.4) to c20f9e7 (v0.80.6) in maintenance and CI tools workflows. Ensure all corresponding .lock workflow files reference the same new github/gh-aw-actions commit to keep lockfiles in sync.	.github/workflows/ci-doctor.lock.yml .github/workflows/agents-md-maintenance.lock.yml .github/workflows/code-simplifier.lock.yml .github/workflows/ci-coach.lock.yml .github/workflows/daily-malicious-code-scan.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/ci_tools.yaml
Bump softprops/action-gh-release from v3.0.0 to v3.0.1 in the build workflow.	Update pinned commit for softprops/action-gh-release from b430933 (v3.0.0) to 718ea10 (v3.0.1) for release creation. Keep release step configuration (files and generate_release_notes) unchanged while updating the action version.	.github/workflows/build.yaml

Possibly linked issues

• #Dependency Dashboard: Yes. This merge-queue PR validates and merges the Renovate dependency updates (Update github/gh-aw-actions action to v0.80.6 #2278, Update softprops/action-gh-release action to v3.0.1 #2279) listed in the dashboard.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[MH0386]

🔍 Vulnerabilities of ghcr.io/alphaspheredotai/chattr:9ecd019-pr-2280

📦 Image Reference ghcr.io/alphaspheredotai/chattr:9ecd019-pr-2280

digest	sha256:c789cc488dd701bb7f72fb812dc7ee04083b0438300aebd9c4688f3b05e5114d
vulnerabilities
platform	linux/amd64
size	282 MB
packages	430

libcrypto3 3.6.2-r2 (apk) pkg:apk/wolfi/libcrypto3@3.6.2-r2?arch=x86_64&origin=openssl # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.222% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 1.409% EPSS Percentile 69th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.358% EPSS Percentile 28th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.297% EPSS Percentile 21st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.332% EPSS Percentile 25th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.408% EPSS Percentile 32nd percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.666% EPSS Percentile 47th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.531% EPSS Percentile 41st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.513% EPSS Percentile 40th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.204% EPSS Percentile 10th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.349% EPSS Percentile 27th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.596% EPSS Percentile 44th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.255% EPSS Percentile 17th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.226% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.210% EPSS Percentile 11th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.252% EPSS Percentile 16th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.351% EPSS Percentile 27th percentile Description

libcrypto3 3.6.2-r2 (apk) pkg:apk/wolfi/libcrypto3@3.6.2-r2?arch=x86_64&distro=wolfi # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.222% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 1.409% EPSS Percentile 69th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.358% EPSS Percentile 28th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.297% EPSS Percentile 21st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.332% EPSS Percentile 25th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.408% EPSS Percentile 32nd percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.666% EPSS Percentile 47th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.531% EPSS Percentile 41st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.513% EPSS Percentile 40th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.204% EPSS Percentile 10th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.349% EPSS Percentile 27th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.596% EPSS Percentile 44th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.255% EPSS Percentile 17th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.226% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.210% EPSS Percentile 11th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.252% EPSS Percentile 16th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.351% EPSS Percentile 27th percentile Description

libssl3 3.6.2-r2 (apk) pkg:apk/wolfi/libssl3@3.6.2-r2?arch=x86_64&distro=wolfi-20230201&upstream=openssl # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.222% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 1.409% EPSS Percentile 69th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.358% EPSS Percentile 28th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.297% EPSS Percentile 21st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.332% EPSS Percentile 25th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.408% EPSS Percentile 32nd percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.666% EPSS Percentile 47th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.531% EPSS Percentile 41st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.513% EPSS Percentile 40th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.204% EPSS Percentile 10th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.349% EPSS Percentile 27th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.596% EPSS Percentile 44th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.255% EPSS Percentile 17th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.226% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.210% EPSS Percentile 11th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.252% EPSS Percentile 16th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.351% EPSS Percentile 27th percentile Description

libcrypto3 3.6.2-r2 (apk) pkg:apk/wolfi/libcrypto3@3.6.2-r2?arch=x86_64&distro=wolfi-20230201&upstream=openssl # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.222% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 1.409% EPSS Percentile 69th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.358% EPSS Percentile 28th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.297% EPSS Percentile 21st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.332% EPSS Percentile 25th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.408% EPSS Percentile 32nd percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.666% EPSS Percentile 47th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.531% EPSS Percentile 41st percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.513% EPSS Percentile 40th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.204% EPSS Percentile 10th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.349% EPSS Percentile 27th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.596% EPSS Percentile 44th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.255% EPSS Percentile 17th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.226% EPSS Percentile 13th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.210% EPSS Percentile 11th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.252% EPSS Percentile 16th percentile Description Affected range <3.6.3-r0 Fixed version 3.6.3-r0 EPSS Score 0.351% EPSS Percentile 27th percentile Description

glibc-locale-posix 2.43-r6 (apk) pkg:apk/wolfi/glibc-locale-posix@2.43-r6?arch=x86_64&distro=wolfi # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

ld-linux 2.43-r6 (apk) pkg:apk/wolfi/ld-linux@2.43-r6?arch=x86_64&distro=wolfi-20230201&upstream=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

libcrypt1 2.43-r6 (apk) pkg:apk/wolfi/libcrypt1@2.43-r6?arch=x86_64&origin=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

glibc 2.43-r6 (apk) pkg:apk/wolfi/glibc@2.43-r6?arch=x86_64&origin=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

libcrypt1 2.43-r6 (apk) pkg:apk/wolfi/libcrypt1@2.43-r6?arch=x86_64&distro=wolfi # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

glibc 2.43-r6 (apk) pkg:apk/wolfi/glibc@2.43-r6?arch=x86_64&distro=wolfi # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

ld-linux 2.43-r6 (apk) pkg:apk/wolfi/ld-linux@2.43-r6?arch=x86_64&distro=wolfi # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

ld-linux 2.43-r6 (apk) pkg:apk/wolfi/ld-linux@2.43-r6?arch=x86_64&origin=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

glibc-locale-posix 2.43-r6 (apk) pkg:apk/wolfi/glibc-locale-posix@2.43-r6?arch=x86_64&distro=wolfi-20230201&upstream=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

libcrypt1 2.43-r6 (apk) pkg:apk/wolfi/libcrypt1@2.43-r6?arch=x86_64&distro=wolfi-20230201&upstream=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

glibc-locale-posix 2.43-r6 (apk) pkg:apk/wolfi/glibc-locale-posix@2.43-r6?arch=x86_64&origin=glibc # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.451% EPSS Percentile 36th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.345% EPSS Percentile 26th percentile Description

busybox 1.37.0-r57 (apk) pkg:apk/wolfi/busybox@1.37.0-r57?arch=x86_64&distro=wolfi # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.710% EPSS Percentile 49th percentile Description Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.154% EPSS Percentile 5th percentile Description Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.664% EPSS Percentile 47th percentile Description

busybox 1.37.0-r57 (apk) pkg:apk/wolfi/busybox@1.37.0-r57?arch=x86_64&origin=busybox # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.710% EPSS Percentile 49th percentile Description Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.154% EPSS Percentile 5th percentile Description Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.664% EPSS Percentile 47th percentile Description

busybox 1.37.0-r57 (apk) pkg:apk/wolfi/busybox@1.37.0-r57?arch=x86_64&distro=wolfi-20230201 # Dockerfile (1:14) FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS builder ARG INSTALL_SOURCE ARG PYTHON_VERSION # skipcq: DOK-DL3018 RUN apk add --no-cache build-base git uv USER nonroot RUN --mount=type=cache,target=/root/.cache/uv \ uv tool install ${INSTALL_SOURCE} --python ${PYTHON_VERSION} FROM cgr.dev/chainguard/wolfi-base:latest@sha256:1af610c4a70668dad46159ee178b20378c79a49b554f76405670fc442d30183a AS production Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.710% EPSS Percentile 49th percentile Description Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.154% EPSS Percentile 5th percentile Description Affected range <1.37.0-r58 Fixed version 1.37.0-r58 EPSS Score 0.664% EPSS Percentile 47th percentile Description

undici 6.25.0 (npm) pkg:npm/undici@6.25.0 # Dockerfile (28:28) COPY --from=builder --chown=nonroot:nonroot --chmod=555 /home/nonroot/.local/ /home/nonroot/.local/ Uncontrolled Resource Consumption Affected range <6.27.0 Fixed version 6.27.0 CVSS Score 7.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H EPSS Score 0.284% EPSS Percentile 20th percentile Description Impact The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (new WebSocket(...)) or the WebSocketStream API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. All releases starting at undici 6.17.0 are affected. Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. Workarounds No workaround is available. The fix must be applied through an upgrade. Improper Neutralization of CRLF Sequences ('CRLF Injection') Affected range <6.27.0 Fixed version 6.27.0 CVSS Score 5.9 CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N EPSS Score 0.205% EPSS Percentile 11th percentile Description Impact undici's cookie parser in parseSetCookie percent-decodes cookie values via qsUnescape, turning encoded sequences like %0D%0A, %00, %3B, and %3D into their literal byte equivalents. RFC 6265 §5.4 does not specify any decoding and browsers do not decode either. Applications that parse a Set-Cookie header and then forward the parsed value into a response header (proxies, middleware, SSR frameworks) become vulnerable to HTTP response header injection: an attacker-controlled upstream can inject arbitrary Set-Cookie, Location, or Cache-Control headers into the application's downstream response, enabling session fixation, open redirect, or cache poisoning. Affected applications are those that use undici's cookie parsing (parseSetCookie, parseCookie, getSetCookies) and forward the parsed cookie value into a response header. This was introduced in undici 7.0.0 via #3789. Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. Workarounds If upgrade is not immediately possible, do not forward values returned by parseSetCookie/parseCookie/getSetCookies directly into response headers; sanitize the value first to strip or reject CR, LF, NUL, ;, and = bytes. Time-of-check Time-of-use (TOCTOU) Race Condition Affected range <6.27.0 Fixed version 6.27.0 CVSS Score 3.7 CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N EPSS Score 0.177% EPSS Percentile 7th percentile Description Impact Undici's HTTP/1.1 client is vulnerable to response queue poisoning on reused keep-alive sockets. An attacker-controlled upstream server can inject an unsolicited HTTP/1.1 response onto an idle socket after a request completes. When the client dispatches the next request on that socket, it associates the injected response with the new request, causing responses to be delivered to the wrong requests. This requires an attacker-controlled or compromised upstream HTTP/1.1 server and keep-alive connection reuse. Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. Workarounds Disable keep-alive connection reuse by setting keepAliveTimeout: 0 on the Client or Pool. Permissive List of Allowed Inputs Affected range <6.27.0 Fixed version 6.27.0 CVSS Score 3.7 CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N EPSS Score 0.197% EPSS Percentile 10th percentile Description Impact When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens: SameSite=NoneOfYourBusiness is parsed as None, the most permissive setting. SameSite=StrictLax is parsed as Lax, a downgrade from Strict. Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide. This was introduced in undici 5.15.0 when the cookies feature was added. Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. Workarounds After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.

pdfjs-dist 3.11.174 (npm) pkg:npm/pdfjs-dist@3.11.174 # Dockerfile (28:28) COPY --from=builder --chown=nonroot:nonroot --chmod=555 /home/nonroot/.local/ /home/nonroot/.local/ Improper Check for Unusual or Exceptional Conditions Affected range <=4.1.392 Fixed version 4.2.67 CVSS Score 8.8 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H EPSS Score 72.648% EPSS Percentile 99th percentile Description Impact If pdf.js is used to load a malicious PDF, and PDF.js is configured with isEvalSupported set to true (which is the default value), unrestricted attacker-controlled JavaScript will be executed in the context of the hosting domain. Patches The patch removes the use of eval: mozilla/pdf.js#18015 Workarounds Set the option isEvalSupported to false. References https://bugzilla.mozilla.org/show_bug.cgi?id=1893645

brace-expansion 5.0.5 (npm) pkg:npm/brace-expansion@5.0.5 # Dockerfile (28:28) COPY --from=builder --chown=nonroot:nonroot --chmod=555 /home/nonroot/.local/ /home/nonroot/.local/ Uncontrolled Resource Consumption Affected range >=5.0.0 <5.0.6 Fixed version 5.0.6 CVSS Score 6.5 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H EPSS Score 0.203% EPSS Percentile 10th percentile Description The max option was being applied too late: When expanding a single large numeric range like {1..10000000}, the sequence generation loop generates all 10 million intermediate elements before the max limit is applied With max=10, the output is correctly limited to 10 items, but the process still allocates ~505 MB and spends ~800ms building the full intermediate array. Workaround Ensure the string to be expanded doesn't contain more values than the desired max item count.

tar 7.5.13 (npm) pkg:npm/tar@7.5.13 # Dockerfile (28:28) COPY --from=builder --chown=nonroot:nonroot --chmod=555 /home/nonroot/.local/ /home/nonroot/.local/ Interpretation Conflict Affected range <=7.5.15 Fixed version 7.5.16 CVSS Score 6.9 CVSS Vector CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N Description Summary 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). node-tar is one of the most widely deployed JavaScript tar libraries (it backs npm's own package-tarball handling and is a transitive dependency of a very large fraction of the npm ecosystem), so the blast radius for "files that extract differently depending on the tool" is broad. This is the same root cause and fix that was just addressed upstream in the Rust tar ecosystem (tar-rs / astral-tokio-tar); node-tar carries the equivalent defect and has no equivalent guard. Impact CWE-436 Interpretation Conflict / inconsistent tar parsing (the same class as the prior tar "smuggling" advisories GHSA-j5gw-2vrg-8fgx and GHSA-fp55-jw48-c537). A crafted archive can present one logical member list to a tool that lists or scans with node-tar and a different member list to GNU tar / libarchive / Python tarfile (and vice versa). This lets a malicious file be hidden from a scanner that uses a different parser than the eventual extractor, or hidden from node-tar-based inspection while still landing on disk via a system tar. No authentication is required; the only precondition is that a victim parses an attacker-supplied tar with node-tar. Tar archives are routinely fetched from untrusted sources (package registries, user uploads, CI artifacts, container layers). Severity: Medium. Impact is integrity-of-archive-interpretation, not direct RCE; it is a building block for supply-chain / scanner-evasion attacks rather than a standalone code-execution primitive. Vulnerable code (file:line) src/header.ts (compiled to dist/esm/header.js:49 and dist/commonjs/header.js:85 in the published tar@<!-- -->7.5.15): // Header.decode(buf, off, ex, gex) this.size = ex?.size ?? gex?.size ?? decNumber(buf, off + 124, 12) ex is the currently-accumulated PAX local extended header and gex the PAX global header. The size override from ex/gex is applied unconditionally to whatever header is being decoded next — there is no check that the header being decoded is a real file entry rather than an intermediary extension header. src/parse.ts, [CONSUMEHEADER] constructs the next header with the current EX/GEX applied: const header = new Header(chunk, position, this[EX], this[GEX]) and later branches on whether that header is a metadata entry. this[EX] is cleared only in the non-meta (real file) branch: if (entry.meta) { // L / K / x / g metadata entries: this[EX] is left intact here if (entry.size > this.maxMetaEntrySize) { entry.ignore = true this[STATE] = 'ignore' entry.resume() } else if (entry.size > 0) { this[META] = '' entry.on('data', c => (this[META] += c)) this[STATE] = 'meta' } } else { this[EX] = undefined // EX cleared only once a real file entry is reached } When the stream is ordered x (PAX, size=N) -> L (GNU long-name) -> file, the L header is constructed with this[EX] still set, so its size/remain becomes N instead of the L payload's true length. node-tar then consumes N bytes of "metadata" and resumes header parsing at the wrong offset, landing mid-stream. Every other mainstream parser applies the PAX size only to the following file entry, so they stay synchronized. The correct behavior (and the fix shipped upstream in the Rust tar ecosystem) is to not apply PAX size/overrides when the entry being decoded is itself an extension header (L GNU long-name, K GNU long-link, x PAX local, g PAX global). How input reaches the sink tar.list(), tar.extract()/tar.x(), and tar.Parse/tar.Unpack all route every 512-byte header block through Header.decode(...) with the currently-accumulated EX/GEX. Any consumer that parses an attacker-supplied archive — tar.list, tar.extract, or piping into the streaming Parser — reaches the sink. No options need to be enabled; the default code path is affected. Proof of concept Archive layout (all standard, GNU-tar-producible blocks): block 0 : x header (PAX local extended, typeflag 'x'), its own size = len(pax body) block 1 : x payload : the single PAX record "...size=2048\n" block 2 : L header (GNU long-name '././@<!-- -->LongLink'), real size = 13 block 3 : L payload : "longname.txt\0" (the long name for the next file) block 4 : file header 'file_a', size = 16 block 5 : file_a body (16 bytes, zero-padded to 512) block 6 : file header 'file_b', size = 16 block 7 : file_b body (16 bytes, zero-padded to 512) Generator (make_tar.py, pure stdlib, no external deps): def hdr(name, size, typeflag): h = bytearray(512); name = name[:100]; h[0:len(name)] = name h[100:108] = b'0000644\0'; h[108:116] = b'0000000\0'; h[116:124] = b'0000000\0' h[124:136] = ('%011o\0' % size).encode(); h[136:148] = b'00000000000\0' h[156:157] = typeflag; h[257:263] = b'ustar\0'; h[263:265] = b'00' h[148:156] = b' ' * 8 cs = sum(h); h[148:156] = ('%06o\0 ' % cs).encode() return bytes(h) def pad(d): return d + b'\0' * ((512 - len(d) % 512) % 512) def pax_record(key, val): # length-prefixed PAX record "LEN key=val\n" body = b' %s=%s\n' % (key.encode(), str(val).encode()); n = len(body) while True: s = str(n).encode() + body if len(s) == n: break n = len(s) return s pax = pax_record('size', 2048) # malicious: claim size=2048 for the "next" entry out = hdr(b'PaxHeaders/x', len(pax), b'x') + pad(pax) out += hdr(b'././@<!-- -->LongLink', 13, b'L') + pad(b'longname.txt\0') out += hdr(b'file_a', 16, b'0') + pad(b'AAAA_file_a_body') out += hdr(b'file_b', 16, b'0') + pad(b'BBBB_file_b_body') out += b'\0' * 1024 open('pax-desync.tar', 'wb').write(out) A negative-control archive is identical except the PAX record is pax_record('comment', 'x') (no size=), written to pax-control.tar. End-to-end reproduction (against pinned version tar@<!-- -->7.5.15, latest release) Install the published package into a clean project and parse both archives: $ npm init -y >/dev/null && npm install tar@<!-- -->7.5.15 $ node -e "console.log(require('tar/package.json').version)" 7.5.15 $ grep -n "ex?.size ?? gex?.size" node_modules/tar/dist/esm/header.js 49: this.size = ex?.size ?? gex?.size ?? decNumber(buf, off + 124, 12); e2e.mjs: import * as tar from 'tar' async function listEntries(f){ const got=[], warns=[] await tar.list({ file:f, onReadEntry:e=>{ got.push({path:e.path,size:e.size,type:e.type}); e.resume() }, onwarn:(code,_msg)=>warns.push(code) }) return { got, warns } } const mal = await listEntries('pax-desync.tar') console.log('MALICIOUS entries :', JSON.stringify(mal.got), 'warnings:', JSON.stringify(mal.warns)) const ctl = await listEntries('pax-control.tar') console.log('CONTROL entries :', JSON.stringify(ctl.got), 'warnings:', JSON.stringify(ctl.warns)) Verbatim output: === Deployed-consumer E2E: npm tar@<!-- -->7.5.15 (latest release) === [MALICIOUS] archive = x(PAX size=2048) -> L(GNU longname "longname.txt") -> file_a(16B) -> file_b(16B) tar.list() entries : [] tar.list() warnings: ["TAR_ENTRY_INVALID"] [NEGATIVE CONTROL] same archive, PAX record is "comment=x" (no size= override) tar.list() entries : [{"path":"longname.txt","size":16,"type":"File"},{"path":"file_b","size":16,"type":"File"}] tar.list() warnings: [] Reference parsers on the same pax-desync.tar: $ tar tvf pax-desync.tar -rw-r--r-- 0 0 0 2048 Jan 1 1970 longname.txt # GNU tar $ bsdtar tvf pax-desync.tar -rw-r--r-- 0 0 0 2048 Jan 1 1970 longname.txt # libarchive $ python3 -c "import tarfile; print([m.name for m in tarfile.open('pax-desync.tar').getmembers()])" ['longname.txt'] # Python tarfile Interpretation differential: GNU tar, libarchive (bsdtar), and Python tarfile all extract the member longname.txt from pax-desync.tar, whereas node-tar 7.5.15 desynchronizes, raises TAR_ENTRY_INVALID (checksum failure from landing mid-stream), and reports zero members. The negative control proves the divergence is caused solely by the PAX size= override being applied to the intermediary L header — when the same archive carries a PAX record without size=, node-tar parses it identically to the reference tools (longname.txt, file_b). Suggested fix When decoding a header, do not apply PAX size (or other PAX overrides) if the header being decoded is itself an extension header. Concretely, in src/parse.ts clear/ignore this[EX] (and this[GEX] for size) when the header's type is ExtendedHeader, GlobalExtendedHeader, NextFileHasLongPath (GNU L), or NextFileHasLongLinkpath (GNU K); equivalently, in Header.decode, gate the ex?.size ?? gex?.size override on the decoded type not being one of those extension types. This mirrors the upstream Rust fix, which guards pax_size with is_gnu_longname || is_gnu_longlink || is_pax_local_extensions || is_pax_global_extensions. A fix PR is being prepared against a private fork and will be linked here. Fix PR To be linked from a private fork of the repository (the fix will not be pushed to any public fork or to upstream during embargo). Credits Reported by tonghuaroot.

ip-address 10.1.0 (npm) pkg:npm/ip-address@10.1.0 # Dockerfile (28:28) COPY --from=builder --chown=nonroot:nonroot --chmod=555 /home/nonroot/.local/ /home/nonroot/.local/ Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') Affected range <=10.1.0 Fixed version 10.1.1 CVSS Score 5.3 CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N EPSS Score 0.258% EPSS Percentile 17th percentile Description Summary Address6.group() and Address6.link() do not HTML-escape attacker-controlled content before embedding it in the HTML strings they return, and AddressError.parseMessage (emitted by the Address6 constructor for invalid input) can contain unescaped attacker-controlled content in one branch. An application that (1) passes untrusted input to Address6 and (2) renders the output of these methods, or the thrown error's parseMessage, as HTML (e.g. via innerHTML) is vulnerable to cross-site scripting. A related issue in v6.helpers.spanAll() produced malformed markup but was not exploitable; it is hardened in the same release for consistency. Details Four related issues were identified and fixed together: Address6.group(): zone ID injection. The Address6 constructor stores the raw input (including any IPv6 zone ID) in this.address before zone stripping. group() then passed this.address to helpers.simpleGroup(), which wrapped each :-separated segment in a <span> element without HTML-escaping the content. A zone ID containing HTML markup was embedded verbatim. Address6.link({ prefix, className }): attribute-value injection. link() concatenated user-supplied prefix and className into the href="…" and class="…" attributes without escaping. A caller passing untrusted content through these options could inject event handlers (e.g. onmouseover) and achieve XSS. Address6 constructor: leading-zero IPv4 error path. The leading-zero branch in parse4in6() built AddressError.parseMessage by concatenating the raw address through String.replace(). Because parse4in6() runs before the bad-character check, any characters in the groups preceding the IPv4 suffix flowed into the error's HTML unescaped. Consumers who render parseMessage as HTML (its documented purpose — it already contains <span class="parse-error"> markup) could be XSS'd by a crafted input such as <img src=x onerror=alert(1)>:10.0.01.1. v6.helpers.spanAll(): attribute-value injection (defense in depth). spanAll() embedded each character of its input into a class="digit value-${n} …" attribute without escaping. Because split('') limits n to a single character this was not exploitable in practice, but it produced malformed markup and is fixed for consistency. Affected Versions All versions up to and including 10.1.0. Patched Version 10.1.1. Impact Real-world exposure is believed to be extremely limited. Analysis of all 425 dependent npm packages as well as GitHub code search found zero consumers of group(), link(), or spanAll(): these HTML-emitting surfaces appear to be unused across published npm packages and public repositories. Applications using only the address-parsing and comparison APIs (isValid, correctForm, isInSubnet, bigInt, etc.) are not affected. Consumers who do render the output of group(), link(), spanAll(), or AddressError.parseMessage as HTML against untrusted input should upgrade. PoC const { Address6 } = require('ip-address'); const addr = new Address6('fe80::1%<img src=x onerror=alert(1)>'); document.body.innerHTML = addr.group(); // fires the onerror handler in 10.1.0 Workarounds If users cannot upgrade immediately: Do not pass untrusted input to the Address6 constructor, or Never render the output of group(), link(), or spanAll(), nor the parseMessage field of any thrown AddressError, as HTML; treat these values as text only, or run them through DOMPurify before inserting into the DOM (DOMPurify's default configuration preserves the library's intended <span> wrapping while stripping any injected event handlers), or Validate input with Address6.isValid() and reject anything that contains a zone identifier (a % character) or characters outside [0-9a-fA-F:/] before passing it to the constructor. Lack of separate CVEs Given the evidence that these methods are not used, and given that they are all of the same construction, maintainers do not think it's relevant or useful to create a separate CVE for each library method. Credit ip-address thanks @scovetta for reporting this issue.