Repository navigation
fix(security): bump next 16.4.2, storybook 10.6.2 - #163
Merged
Merged
Conversation
next is pinned at ^16.4.1 in security/overrides.yaml and resolves 16.4.2, which clears GHSA-2464-fhr4-w9xw (critical), GHSA-673q-mjm6-r5xr (critical) and GHSA-p3m5-59mp-jv5r (high). Only the first has a sink in the image, the sharp the image optimiser loads, and the lockfile already resolved sharp 0.35.5, its fix. The pin raises next's own sharp floor to match, and it survives the sync merge driver, which takes upstream's lockfile. storybook and its @storybook/* family move to 10.6.2 by yarn up -R inside their declared ranges, clearing GHSA-f2ph-cmg5-wxc8 (critical) and GHSA-px85-f4q5-jh77 (high). builder-webpack5 10.6.2 no longer depends on @vitest/mocker, which clears GHSA-qxg6-89mg-rqv8 (moderate). All three are dev only: storybook is an app devDependency and none of the family reaches the image. ip-address moves to 10.7.4 the same way for GHSA-rxp7-6hxx-x8q5 (moderate). It ships in the api, but both callers hand it a URL-parsed hostname, which cannot hold the % and line terminator the advisory needs. osv-scanner.toml drops the GHSA-82fw-gwwq-j7x9 ignore the scanner no longer reports, and the ip-address triage verdict names the versions the lockfile now resolves.
Contributor
|
Released in v0.3.12 -- https://github.com/hyperi-io/dfe-hyperdx/releases/tag/v0.3.12 |
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.
Summary
Clears Dependabot alerts 360 to 366 for the 2.2.1 GA candidate: three against next, two against storybook, one each against ip-address and @vitest/mocker. Three of them are critical.
next (alerts 363, 366, 362)
images.unoptimizedsits only in the static-export branch ofpackages/app/next.config.mjs:180, so/_next/imageloads sharp. It was already mitigated: the lockfile has resolved sharp 0.35.5, the advisory's fix, since 2026-10-09. 16.4.1 raises next's own floor tosharp ^0.35.5, so the fix stops resting on one lockfile entry.use cachefunction returning typed arrays.packages/appis Pages Router, noapp/directory, nouse cache.next ^16.4.1insecurity/overrides.yaml, rather thanyarn up -R, because the sync merge driver takes upstream's lockfile. That is how the 2.40.0 sync took next 16.3.6 back to 16.3.4. Upstream has the same bump open as chore(deps): bump next from 16.3.8 to 16.4.1 ClickHouse/ClickStack#3460, and--checknags to drop the pin once upstream's lockfile passes it.--applywrote oneresolutionskey.yarn installtook 16.4.2 (2026-10-15), becausenpmMinimalAgeGateholds 16.4.3 (2026-10-23). The lockfile moves next,@next/env, the nine@next/swc-*binaries and next's sharp descriptor, nothing else.storybook (alerts 360, 365) and @vitest/mocker (alert 361)
packages/app/package.json:151). @vitest/mocker 3.2.4 came only from@storybook/builder-webpack510.1.4's exact pin. None of the family is in Next's standalone trace or the api's production closure.yarn storybook, and every declared range admits 10.6.2. Nopackage.jsonchange:yarn up -R storybook @storybook/nextjs @storybook/addon-docs @storybook/addon-links @storybook/addon-themes.@storybook/nextjspins its builder exactly, and builder-webpack5 10.6.2 drops @vitest/mocker altogether, which clears 361.osv-scanner.tomldrops GHSA-82fw-gwwq-j7x9, the earlier @vitest/mocker advisory, because the scanner no longer reports it.ip-address (alert 364, GHSA-rxp7-6hxx-x8q5, moderate)
@hyperdx/apideclares it, and express-rate-limit 8.7.1 and socks 2.8.10 pull it too.validateWebhookUrl(utils/validators.ts:161) andPOST /clickhouse-proxy/test(routers/api/clickhouseProxy.ts:105), handisPrivateIpanew URL()hostname. Node's URL parser refuses a host holding%or a line feed, and the quadratic path needs both.yarn up -R ip-addresstakes 10.7.4 inside every declared range, five lockfile lines.scripts/dismiss-triaged-alerts.pynamed^10.3.1and 10.3.1, two syncs stale. It now names^10.7.1and 10.7.4.Measured on this branch
yarn.lockwithosv-scanner.toml: main 11 (3 critical, 6 high, 2 medium), here 4 high, all GHSA-mrhx-c7xc-m3w5 against zod, which this change does not touch.yarn npm audit --severity moderate(the CI gate): no suggestions. With--recursive: smol-toml 1.6.1, the existing nx verdict.scripts/security-override.py --verify: matches, 16 entries (+3 fork pins), both patches applied.--check: all three pins holding, upstream ships next 16.3.6.nx run-many --target=buildfor common-utils, api and app withNEXT_OUTPUT_STANDALONE=true, as the Dockerfile runs it: built on Next 16.4.2. The standalone trace carries next 16.4.2 and sharp 0.35.5.yarn workspaces focus @hyperdx/api --production: of the 199 versions the lockfile adds, only ip-address 10.7.4 lands in the api's production closure.validators.test.tsincluded. App unit suite 303 suites, 4692 tests passed.storybook buildcompletes on 10.6.2.yarn install --immutableclean. Fork tooling tests 61 OK. Fork-surface guard passes onorigin/main...HEAD.hyperi-ci check --quickpasses (eslint, prettier, tsc, audit, semgrep, gitleaks), osv-scanner non-blocking on zod.Not measured: no image built or deployed, no e2e, no
storybook devsession.Still to land on this branch before merge: the
resolutionsline indocs/fork/what-we-changed.md(two generated pins become three) and the dated section indocs/fork/security-sync.md.Done when this merges and Dependabot closes 360 to 366 as fixed. Nothing needs dismissing.