fix: upgrade brace-expansion to 5.0.7, 1.1.16, 2.1.2 (CVE-2026-13149) - #10749
fix: upgrade brace-expansion to 5.0.7, 1.1.16, 2.1.2 (CVE-2026-13149)#10749anupamme wants to merge 1 commit into
Conversation
Automated dependency upgrade by OrbisAI Security
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 691b6c2346
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "@inkeep/docusaurus": "^2.0.16", | ||
| "@mdx-js/react": "^3.0.0", | ||
| "autoprefixer": "^10.4.17", | ||
| "brace-expansion": "^1.1.16", |
There was a problem hiding this comment.
Upgrade the nested 2.x brace-expansion copy too
Adding brace-expansion as a top-level dependency only fixes the hoisted 1.x instance; the lockfile still pins node_modules/glob/node_modules/brace-expansion to 2.0.2 at documentation/package-lock.json:9632, which falls in the GitHub advisory's vulnerable >=2.0.0, <2.1.2 range (GHSA-3jxr-9vmj-r5cp). Because glob is still pulled via tailwindcss -> sucrase, scanners that inspect the lockfile will continue to report CVE-2026-13149, so please update or override that transitive copy to 2.1.2 as well.
Useful? React with 👍 / 👎.
|
Thanks for taking a look! I filed another PR which addresses the codex comment #10842, as we need to address it at the lockfile level. |
Summary
Upgrade brace-expansion from 1.1.12 to 5.0.7, 1.1.16, 2.1.2 to fix CVE-2026-13149.
Vulnerability
CVE-2026-13149documentation/package-lock.jsonDescription: brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity
Evidence
Scanner confirmation: trivy rule
CVE-2026-13149flagged this pattern.Production code: This file is in the production codebase, not test-only code.
Threat Model Context
This is a containerized service - vulnerabilities may be exploitable depending on network exposure.
Changes
documentation/package.jsondocumentation/package-lock.jsonBehavior Preservation
The change is scoped to 2 files on the vulnerable path, and the project's existing tests still pass, so intended behavior is unchanged.
Verification
This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.
Automated security fix by OrbisAI Security