Skip to content

fix(deps): bump next in apps/web to ^16.3.3 for GHSA-p293-qw3h-jr36 - #1668

Open
aniruddhaadak80 wants to merge 1 commit into
supermemoryai:mainfrom
aniruddhaadak80:fix/security-next-ghsa-p293
Open

aniruddhaadak80 wants to merge 1 commit into
supermemoryai:mainfrom
aniruddhaadak80:fix/security-next-ghsa-p293

Conversation

@aniruddhaadak80

@aniruddhaadak80 aniruddhaadak80 commented Sep 14, 2026 •

Copy link
Copy Markdown

Summary

Patches GHSA-p293-qw3h-jr36 (CVE-2026-75604, CVSS 9.0): unauthenticated remote code execution via path traversal on Windows-hosted Next.js servers. There is no workaround; the fix is to upgrade Next.js.

This follows up #1655, which bumped chatapp, sdk-playground, and memory-graph-playground to ^16.3.3 but left apps/web on ^16.0.11. That range is still affected (>=16.0 <16.3.3).

What changed

  • apps/web/package.json: next ^16.0.11 → ^16.3.3
  • Root bun.lock regenerated with bun install --lockfile-only so apps/web resolves next 16.3.4 (patched: 16.3.3)

Why

apps/web is the production Next.js app. Leaving it below 16.3.3 keeps the Windows-hosted RCE advisory open even after #1655. Bumping the declared range and lockfile puts web on the same patched line as the other Next apps.

Related

Testing

  • Lockfile resolves next@16.3.4 (>= patched 16.3.3)
  • Change is dependency-only (manifest + lockfile); no application source changes

Breaking changes

None expected. This is a patch-line Next.js bump (16.0.x → 16.3.x) with no public API changes in this repo.

GHSA-p293-qw3h-jr36 (CVE-2026-75604, critical): unauthenticated RCE on Windows-hosted Next.js servers. apps/web was on ^16.0.11 (affected: >=16.0 <16.3.3). bun.lock regenerated (resolves next 16.3.4). Follows up supermemoryai#1655, which covered chatapp, sdk-playground and memory-graph-playground but missed web.
@aniruddhaadak80 aniruddhaadak80 changed the title fix(deps): bump next to ^16.3.3 in web, patches GHSA-p293-qw3h-jr36 fix(deps): bump next in apps/web to ^16.3.3 for GHSA-p293-qw3h-jr36 Sep 21, 2026

This branch has not been deployed

No deployments
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