fix(deps): take Next.js 16.3.3 in the benchmark fixture and watch that manifest - #439
Merged
Merged
Conversation
…t manifest Two critical advisories stood open against `benchmark/bun-next`: unauthenticated remote code execution in the image-optimization API when AVIF files are used, and unauthenticated RCE on Windows-hosted servers. Both are fixed in 16.3.3 and the fixture pinned 16.3.0 exactly. It is a benchmark, not shipped code, which changes the severity but not the argument: a critical advisory that nobody can act on is indistinguishable from one nobody has noticed yet. The reason nobody acted is the second half of this change. `.github/ dependabot.yml` declared `gomod` and `github-actions` only, so no ecosystem watched this manifest at all. The advisory scanner found it -- and opens no pull request. An npm entry for `/benchmark/bun-next` closes that: Bun reads the same `package.json` and `bun.lock` the npm ecosystem does. The lockfile was regenerated with `bun install --lockfile-only`; the diff is confined to `next` and its `@next/*` companions, with no format change. Claude-Session: https://claude.ai/code/session_01CKXKXND4zAgWisTtatyTHX
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.
Two critical advisories stand open against
benchmark/bun-next: unauthenticated remote code execution in the image-optimization API when AVIF files are used, and unauthenticated RCE on Windows-hosted servers. Both are fixed in 16.3.3; the fixture pinned16.3.0exactly.It is a benchmark, not shipped code. That changes the severity, not the argument — a critical advisory nobody can act on looks exactly like one nobody has noticed yet.
Why nobody acted is the second half of this change.
.github/dependabot.ymldeclaredgomodandgithub-actionsonly, so no ecosystem watched this manifest at all. The advisory scanner found the vulnerability and opens no pull request; Dependabot opens pull requests and was not looking. Between them the finding had nowhere to go. Annpmentry for/benchmark/bun-nextcloses that — Bun reads the samepackage.jsonandbun.lockthe npm ecosystem does.The lockfile was regenerated with
bun install --lockfile-only. The diff is confined tonextand its ten@next/*companions moving 16.3.0 → 16.3.3, with no lockfile-format change and no unrelated churn — checked, because the local Bun is 1.4.0 while this fixture declaresbun@1.3.14.Verification:
go build ./...clean;bun installresolved 63 packages and saved the lockfile without error.https://claude.ai/code/session_01CKXKXND4zAgWisTtatyTHX