Repository navigation
Fix all open dependency security advisories - #509
Merged
Merged
Conversation
next 16.2.6 is affected by five critical advisories, including remote code execution in next/og ImageResponse (GHSA-vcvr-r3jv-pc5j) and in the Image Optimization API for SVG and AVIF files (GHSA-2464-fhr4-w9xw, GHSA-2xp9-vwfh-vxw4), plus several high-severity SSRF and DoS issues. 16.4.3 resolves all of them and brings sharp 0.35.5, which clears its libvips advisories. 16.4.4 is newer but its @next/* packages are still inside bunfig's minimumReleaseAge window.
bun audit still reported 54 advisories (1 critical, 27 high) after the Next.js upgrade, mostly in transitive packages that Dependabot does not surface from bun.lock. - @cursor/sdk 1.0.12 -> 1.2.0 drops sqlite3 and its node-gyp/prebuild tree, which removes the undici, tar@6, @fastify/busboy, ip-address, brace-expansion and @tootallnate/once advisories. 1.2.0 removed the `platform` option, so the scan now passes the tmpfs state root through an explicit SqliteLocalAgentStore (built on node:sqlite) as `local.store` and disposes it after each scan. - next-safe-action 8.5.2 -> 8.7.3 drops deepmerge-ts. - tar, nanoid, postcss and zod bumped to patched versions; the root zod override/resolution moves with them so nested copies stay aligned. - Stale nested lockfile entries for postcss, nanoid, source-map-js and baseline-browser-mapping re-resolved to the patched hoisted versions. bun audit now reports no vulnerabilities. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Fixes every advisory reported by Dependabot and
bun audit. After this PR,bun auditreports no vulnerabilities.Next.js 16.2.6 -> 16.4.3
Covers all 20 open Dependabot alerts, including the critical RCEs in
next/ogImageResponse(GHSA-vcvr-r3jv-pc5j) and the Image Optimization API for SVG/AVIF (GHSA-2464-fhr4-w9xw, GHSA-2xp9-vwfh-vxw4), plus several high-severity SSRF and DoS issues. Also brings sharp 0.35.5, which clears its libvips advisories. 16.4.4 is newer, but its@next/*packages are still inside bunfig'sminimumReleaseAgewindow.Transitive advisories (only visible to
bun audit)bun auditreported 54 more advisories (1 critical, 27 high) in packages Dependabot doesn't surface frombun.lock:@cursor/sdk1.0.12 -> 1.2.0 dropssqlite3and its node-gyp/prebuild tree, which removes theundici,tar@6,@fastify/busboy,ip-address,brace-expansionand@tootallnate/onceadvisories.next-safe-action8.5.2 -> 8.7.3 dropsdeepmerge-ts.tar,nanoid,postcss,zodbumped to patched versions. The rootzodoverride/resolution moves to 4.6.7 so nested copies stay on one version (the reason it was pinned in the first place).postcss,nanoid,source-map-jsandbaseline-browser-mappingnow resolve to the patched hoisted versions.Code change: plugin scan state root
SDK 1.2.0 removed the
platformoption the scan used to keep the SDK's run store on writable tmpfs (#395). The scan now opens aSqliteLocalAgentStore(built onnode:sqlite, no native module) at the same tmpstateRoot, passes it aslocal.store, and disposes it when the scan finishes.Testing
bunx biome ci .andbun run typecheckpass.bun install --frozen-lockfilesucceeds andbun auditis clean.next buildcompiles and typechecks. Locally it then stops at the known empty-databasegenerateStaticParamscheck, so the Vercel preview is the full build check.SqliteLocalAgentStoreopensindex.dbunder a tmp state root and disposes cleanly on Node 24.next dev(Node): queued a test plugin pointing atoctocat/Hello-World, triggered/api/queue/plugin-scans/drain, and the scan downloaded the repo, ran composer-2 throughAgent.promptwith the new store, and wrote asafeverdict. The SDK state landed in<tmp>/cursor-sdk-home/sdk-agent-store/index.db, and the store closed cleanly.