fix: patch the ten advisories that reach production - #15
Open
PouyanJay wants to merge 1 commit into
Open
Conversation
next 16.2.6 -> 16.3.0 and react-server-dom-webpack 19.2.6 -> 19.2.8, covering every npm advisory that reaches the browser or the server runtime: SSRF in rewrites and in Server Actions, cache confusion of response bodies, unauthenticated disclosure of internal Server Function endpoints, DoS in the Image Optimization API, and a DoS in Server Functions. react and react-dom move 19.2.6 -> 19.2.8 with them, because react-server-dom-webpack@19.2.8 peers on react@^19.2.8 and npm will not resolve the tree otherwise. Both are patch releases. Deliberately narrow. The remaining 15 advisories are all build- or dev-time — vite, wrangler, miniflare, undici, ws, sharp, esbuild — and their fixes want versions outside the exact pins this project uses, so they need their own change and their own testing. Fixes thebuggeddev#12
|
@PouyanJay is attempting to deploy a commit to the thebuggeddev-9222's projects Team on Vercel. A member of the Team first needs to authorize it. |
PouyanJay
force-pushed
the
fix/12-security-bumps
branch
from
August 7, 2026 07:46
e9f7578 to
7bf5ce0
Compare
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.
Fixes #12.
The change
nextreact-server-dom-webpackreact/react-domReact had to move too.
react-server-dom-webpack@19.2.8peers onreact@^19.2.8, so npm refuses to resolve the tree while React is pinned at 19.2.6. Both are patch releases. This is the kind of ripple that's much easier to reason about — and revert — in its own PR, which is why the bumps weren't folded into #9.Result
npm auditgoes 18 → 15. All four production-facing packages report clean:The remaining 15 are entirely build- and dev-time (
vite,wrangler,miniflare,undici,ws,sharp,esbuild,postcss). Their fixes want versions outside this project's exact pins, so they're deliberately left for a separate change with its own testing. #13 removes three more of them by deleting the unused drizzle scaffolding.Verification
vinext buildsucceeds on 16.3.0 — the main risk with a Next minortsc --noEmitclean,eslint appcleannpm testfails on this branch in isolation, becausemainstill carries the broken starter test that #14 fixes — the failure is pre-existing and unrelated to the bump. I verified the bump by merging #14 into a scratch branch and running the suite there, which is where the 6/6 above comes from.