chore(deps)(deps-dev): bump brace-expansion from 1.1.14 to 1.1.16 - #217
chore(deps)(deps-dev): bump brace-expansion from 1.1.14 to 1.1.16#217dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 1.1.14 to 1.1.16. - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](juliangruber/brace-expansion@v1.1.14...v1.1.16) --- updated-dependencies: - dependency-name: brace-expansion dependency-version: 1.1.16 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Security review — PR #217
Verdict: No high-confidence vulnerabilities introduced by this diff.
This pull request is a dependency remediation: it updates package-lock.json only and bumps all resolved brace-expansion copies to patched releases (1.1.14 → 1.1.16 in nested dev trees; 5.0.6 → 5.0.8 at the top level). No application source, config, or workflow logic changes.
Threat-model checklist (diff-scoped)
| Area | Result |
|---|---|
| Injection (SQL/command/template/path) | Not applicable — no runtime code changes |
| Authn/authz bypass | Not applicable |
| Secrets / token leakage | Not applicable |
| Deserialization, SSRF, XSS, CSRF | Not applicable |
| Supply chain | Remediation — addresses CVE-2026-13149 (DoS via exponential brace expansion) |
Confirmed findings
None. The diff does not introduce exploitable behavior.
Remediation already present in this PR
All six brace-expansion lockfile entries now resolve to patched versions (1.1.16 or 5.0.8), which are the fixed releases for CVE-2026-13149. Merging this PR reduces prior DoS exposure in dev/build tooling (ESLint, rimraf, tmp, minimatch/glob consumers).
Residual risk / assumptions (informational, not blocking)
- Runtime exposure is low for this repo.
brace-expansionis transitive in dev/build tooling, not shipped to the static Astro site. Exploitation requires attacker-controlled strings reachingexpand()(e.g. via glob/minimatch brace patterns). That path is not evident in production runtime for this portfolio. - Node engine metadata change.
brace-expansion@5.0.8declaresnode: "20 || >=22"(Node 18 removed). This is an operational compatibility note, not a security defect; confirm CI/dev environments meet that constraint. - CI format failure is unrelated. The
Lint, format, type-check, auditjob failed on Prettier checks in unrelated files, not on audit findings forbrace-expansion.
Recommendation
Approve from a security perspective. Merge to complete the CVE remediation. No additional security-driven code changes are required in this PR.
Sent by Cursor Automation: Find vulnerabilities


Bumps brace-expansion from 1.1.14 to 1.1.16.
Release notes
Sourced from brace-expansion's releases.
Commits
447763a1.1.16d74e630fix: v1 backport for CVE-2026-13149 (#122)2203f4f1.1.150b09384Backport v5.0.6 change to v1 (#111)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.