security: patch dependency vulnerabilities (Next.js, next-intl, postcss, picomatch)#22
Merged
Merged
Conversation
…ss, picomatch) npm audit found 10 vulnerabilities (4 high, 5 moderate, 1 low): multiple Next.js CVEs (SSRF via WebSocket upgrades, middleware/proxy bypasses, cache poisoning, XSS, DoS), a next-intl open redirect + prototype pollution issue, and transitive picomatch/postcss/ajv/brace-expansion advisories. - next 16.1.4 -> 16.2.10, eslint-config-next matched to same version - npm audit fix for next-intl, picomatch, ajv, brace-expansion, @babel/core - added postcss override (^8.5.10) to patch the copy Next.js bundles internally, which still shipped a vulnerable postcss even after the 16.2.10 bump npm audit now reports 0 vulnerabilities. Verified npm run build and npm run lint both pass clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
✅ Deploy Preview for ai-stock-alert-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
main(21 high, 19 moderate, 6 low); localnpm auditmatched a subset of 10 before this fix.next16.1.4 → 16.2.10 (fixes the bulk of the high-severity Next.js CVEs: SSRF via WebSocket upgrades, middleware/proxy bypasses, cache poisoning, DoS, XSS).eslint-config-nextbumped to match.npm audit fixfornext-intl(open redirect + prototype pollution),picomatch(ReDoS/method injection),ajv,brace-expansion,@babel/core.postcssoverride (^8.5.10) because Next.js 16.2.10 still bundles its own vulnerable nestedpostcss@8.4.31internally — the override forces the patched version across the whole tree.flattedandminimatch(both flagged by Dependabot as transitive high-severity issues) were swept to patched versions automatically as part of the lockfile refresh.Local
npm auditnow reports 0 vulnerabilities.Test plan
npm run build— succeeds, all 23 static routes generate correctlynpm run lint— clean🤖 Generated with Claude Code