Skip to content

chore(deps): update next to ^16.2.3 [SECURITY]#76

Closed
yahyafakhroji wants to merge 1 commit intomainfrom
chore/next-security-fix
Closed

chore(deps): update next to ^16.2.3 [SECURITY]#76
yahyafakhroji wants to merge 1 commit intomainfrom
chore/next-security-fix

Conversation

@yahyafakhroji
Copy link
Copy Markdown
Contributor

Summary

Patches Next.js to 16.2.3 to remediate GHSA-q4gf-8mx6-v5v3 / CVE-2026-23869. A crafted HTTP request to any App Router Server Function endpoint can trigger excessive CPU use during React Server Components deserialization, causing DoS.

Supersedes #69. Narrower diff because only apps/docs uses Next — the library packages and storybook don't.

Fumadocs compatibility

Verified against current installation (fumadocs-core, fumadocs-ui @ 16.6.17, fumadocs-mdx @ 14.2.10):

Package Peer next range Status vs 16.2.3
fumadocs-core@16.6.17 16.x.x
fumadocs-ui@16.6.17 16.x.x
fumadocs-mdx@14.2.10 ^15.3.0 || ^16.0.0

No fumadocs bump required for the CVE fix. Latest is fumadocs-*@16.7.14 — left for a future Renovate PR since it's unrelated to the security issue.

Test plan

  • pnpm install — clean resolution, next resolves to 16.2.3 across all importers (fumadocs-core/mdx/ui, nuqs)
  • pnpm --filter @repo/docs build — succeeds, 75 static pages, TypeScript passes
  • CI: lint, typecheck, test, build all green

After merge

Close #69.

Addresses GHSA-q4gf-8mx6-v5v3 (CVE-2026-23869): a specially crafted HTTP
request to an App Router Server Function endpoint can trigger excessive
CPU usage via React Server Components deserialization, causing denial of
service. Fixed in Next.js 16.2.3.

Supersedes #69. Only the docs app uses Next; storybook and library
packages are unaffected.

Fumadocs compatibility verified: fumadocs-core@16.6.17 and
fumadocs-ui@16.6.17 declare peer next: "16.x.x"; fumadocs-mdx@14.2.10
declares peer next: "^15.3.0 || ^16.0.0". All satisfied by 16.2.3, no
fumadocs bump required.

Validated: apps/docs next build succeeds on 16.2.3 (75 static pages,
TypeScript passes).
@yahyafakhroji
Copy link
Copy Markdown
Contributor Author

Closing — folding the security fix into #75. See updated PR description there.

@yahyafakhroji yahyafakhroji deleted the chore/next-security-fix branch April 13, 2026 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant