Pin github/gh-aw-actions action to efa5584 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github/gh-aw-actions	action	pinDigest	→ efa5584

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.github/workflows/agents-md-maintenance.lock.yml	0% smaller
.github/workflows/ci-coach.lock.yml	0% smaller
.github/workflows/ci-doctor.lock.yml	0% smaller
.github/workflows/code-simplifier.lock.yml	0% smaller
.github/workflows/daily-malicious-code-scan.lock.yml	0% smaller

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-23 02:10 UTC · Rule: Github Actions Updates
• ✅ Checks started · on draft merge queue: embarking main (139da33) and [#1953 + #1954] together #1955
• 🚫 Left the queue — 2026-05-23 02:13 UTC · at 07b1eb7ac07995bbc2920c8dd4cc5cc64eb4f3f2

This pull request spent 2 minutes 43 seconds in the queue, with no time running CI.

Waiting for any of

• check-neutral = Mergify Merge Protections
• check-skipped = Mergify Merge Protections
• check-success = Mergify Merge Protections

All conditions

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

Reason

The pull request #1953 has been manually updated

Hint

If you want to requeue this pull request, you can post a @mergifyio queue comment.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-23 02:15 UTC · Rule: Github Actions Updates
• 🚫 Left the queue — 2026-05-23 02:22 UTC · at bcfbbf3f06e5880f5eb7eb7293c7371c20ba7d4f

This pull request spent 7 minutes 13 seconds in the queue, with no time running CI.

Reason

The pull request #1953 has been manually updated

Hint

If you want to requeue this pull request, you can post a @mergifyio queue comment.

[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

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-23 02:22 UTC · Rule: Github Actions Updates
• 🚫 Left the queue — 2026-05-23 02:24 UTC · at ec67b832d100c51f639581201ad31fd672d03d0a

This pull request spent 1 minute 28 seconds in the queue, with no time running CI.

Reason

The pull request conflicts with the base branch

Hint

You should update or rebase your pull request.

If you want to requeue this pull request, you can post a @mergifyio queue comment.

[mergify]

Hi @renovate[bot], Your PR is in conflict and cannot be merged.

[mergify]

👋 renovate[bot] your PR is conflicting and needs to be updated to be merged

[mergify]

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CONFLICT_WITH_BASE_BRANCH. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

[MH0386]

🔍 Vulnerabilities of ghcr.io/alphaspheredotai/chattr:44448e3-pr-1953

📦 Image Reference ghcr.io/alphaspheredotai/chattr:44448e3-pr-1953

digest	sha256:869cf32dff832d91f79288613c8d96865eaa40ac072beae79de502021de2342b
vulnerabilities
platform	linux/amd64
size	269 MB
packages	425

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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th 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.049% EPSS Percentile 15th percentile Description Affected range <2.43-r7 Fixed version 2.43-r7 EPSS Score 0.046% EPSS Percentile 14th percentile Description

picomatch 4.0.3 (npm) pkg:npm/picomatch@4.0.3 # Dockerfile (28:28) COPY --from=builder --chown=nonroot:nonroot --chmod=555 /home/nonroot/.local/ /home/nonroot/.local/ Inefficient Regular Expression Complexity Affected range >=4.0.0 <4.0.4 Fixed version 4.0.4 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.019% EPSS Percentile 5th percentile Description Impact picomatch is vulnerable to Regular Expression Denial of Service (ReDoS) when processing crafted extglob patterns. Certain patterns using extglob quantifiers such as +() and *(), especially when combined with overlapping alternatives or nested extglobs, are compiled into regular expressions that can exhibit catastrophic backtracking on non-matching input. Examples of problematic patterns include +(a|aa), +(*|?), +(+(a)), *(+(a)), and +(+(+(a))). In local reproduction, these patterns caused multi-second event-loop blocking with relatively short inputs. For example, +(a|aa) compiled to ^(?:(?=.)(?:a|aa)+)$ and took about 2 seconds to reject a 41-character non-matching input, while nested patterns such as +(+(a)) and *(+(a)) took around 29 seconds to reject a 33-character input on a modern M1 MacBook. Applications are impacted when they allow untrusted users to supply glob patterns that are passed to picomatch for compilation or matching. In those cases, an attacker can cause excessive CPU consumption and block the Node.js event loop, resulting in a denial of service. Applications that only use trusted, developer-controlled glob patterns are much less likely to be exposed in a security-relevant way. Patches This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. Workarounds If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include: disable extglob support for untrusted patterns by using noextglob: true reject or sanitize patterns containing nested extglobs or extglob quantifiers such as +() and *() enforce strict allowlists for accepted pattern syntax run matching in an isolated worker or separate process with time and resource limits apply application-level request throttling and input validation for any endpoint that accepts glob patterns Resources Picomatch repository: https://github.com/micromatch/picomatch lib/parse.js and lib/constants.js are involved in generating the vulnerable regex forms Comparable ReDoS precedent: CVE-2024-4067 (micromatch) Comparable generated-regex precedent: CVE-2024-45296 (path-to-regexp) Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') Affected range >=4.0.0 <4.0.4 Fixed version 4.0.4 CVSS Score 5.3 CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N EPSS Score 0.057% EPSS Percentile 18th percentile Description Impact picomatch is vulnerable to a method injection vulnerability (CWE-1321) affecting the POSIX_REGEX_SOURCE object. Because the object inherits from Object.prototype, specially crafted POSIX bracket expressions (e.g., [[:constructor:]]) can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression. This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control. All users of affected picomatch versions that process untrusted or user-controlled glob patterns are potentially impacted. Patches This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. Workarounds If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include: Sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like [[:...:]]. Avoiding the use of POSIX bracket expressions if user input is involved. Manually patching the library by modifying POSIX_REGEX_SOURCE to use a null prototype: const POSIX_REGEX_SOURCE = { __proto__: null, alnum: 'a-zA-Z0-9', alpha: 'a-zA-Z', // ... rest unchanged }; Resources fix for similar issue: fix: exception when glob pattern contains constructor micromatch/picomatch#144 picomatch repository https://github.com/micromatch/picomatch

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 38.342% EPSS Percentile 97th 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.4 (npm) pkg:npm/brace-expansion@5.0.4 # 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 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. Uncontrolled Resource Consumption Affected range >=4.0.0 <5.0.5 Fixed version 5.0.5 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.024% EPSS Percentile 7th percentile Description Impact A brace pattern with a zero step value (e.g., {1..2..0}) causes the sequence generation loop to run indefinitely, making the process hang for seconds and allocate heaps of memory. The loop in question: https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L184 test() is one of https://github.com/juliangruber/brace-expansion/blob/daa71bcb4a30a2df9bcb7f7b8daaf2ab30e5794a/src/index.ts#L107-L113 The increment is computed as Math.abs(0) = 0, so the loop variable never advances. On a test machine, the process hangs for about 3.5 seconds and allocates roughly 1.9 GB of memory before throwing a RangeError. Setting max to any value has no effect because the limit is only checked at the output combination step, not during sequence generation. This affects any application that passes untrusted strings to expand(), or by error sets a step value of 0. That includes tools built on minimatch/glob that resolve patterns from CLI arguments or config files. The input needed is just 10 bytes. Patches Upgrade to versions 5.0.5+ A step increment of 0 is now sanitized to 1, which matches bash behavior. Workarounds Sanitize strings passed to expand() to ensure a step value of 0 is not used.

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.036% EPSS Percentile 11th 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.