Repository navigation
fix: update next to 15.5.28, disable image optimizer, label server action probes in sentry - #1448
Merged
Merged
Conversation
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
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.
Changes
Next.js
^15.5.28Fixes GHSA-xqc2-xf4c-x3h3 (RSC RCE), GHSA-2464-fhr4-w9xw (image optimizer SVG RCE), GHSA-2xp9-vwfh-vxw4 (image optimizer AVIF RCE), GHSA-p3m5-59mp-jv5r (server action DoS), and the earlier DoS, SSRF. its not really likely we will be target by it.sharp^0.35.5override: the workaround listed for the SVG RCE.images.unoptimized: true: nothing usesnext/image, so/_next/imagenow returns 404 instead of exposing the optimizer. The unusedremotePatternsare gone too, includingcloudflare-ipfs.com.Sentry labels for server action probes. Scanners (React2Shell-style) POST garbage to pages like
/login, which shows up as rawSyntaxError: Expected ',' or '}'…issues.onRequestErrornow spots these and reports them as two warning-level issues, each with a fixed fingerprint and aprobetag:MalformedServerAction(probe:malformed-server-action): the payload didn't decode. Almost always a scanner.UnknownServerAction(probe:unknown-server-action): the action ID doesn't exist. Either a stale tab after a deploy or a scanner.The original error stays attached as
cause. Theprobecontext records the user agent, the action ID and the forwarded IP. Everything else goes throughcaptureRequestErroras before.Also in this PR
minio/minioandminio/mcare gone from Docker Hub and quay.io, so they're nowpgsty/minio:RELEASE.2026-08-04T00-00-00Zandpgsty/mc:RELEASE.2026-10-18T00-00-00Z, the community fork. The healthcheck and the bucket and user setup were tested locally against the test compose file.azure.archive.ubuntu.commirror before running apt.