Skip to content

chore: upgrade @humanfs/node to 0.16.8 to address GHSA-p498-v437-472g - #1630

Merged
brendan-kellam merged 3 commits into
mainfrom
cursor/cve/humanfs-node
Sep 9, 2026
Merged

chore: upgrade @humanfs/node to 0.16.8 to address GHSA-p498-v437-472g#1630
brendan-kellam merged 3 commits into
mainfrom
cursor/cve/humanfs-node

Conversation

@claude

@claude claude Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Fixes SOU-2142

Refreshes the yarn.lock entry for @humanfs/node from 0.16.7 to 0.16.8 to address GHSA-p498-v437-472g (Dependabot alert 334): recursive copy followed symlinked files, so copyAll()/copy() could read and copy data from outside the source tree.

Details

  • @humanfs/node is a transitive dependency: eslint@9.39.3 → @humanfs/node@^0.16.6.
  • The existing ^0.16.6 range already admits the patched 0.16.8, so this is a lockfile refresh only (yarn up -R @humanfs/node). No package.json change and no resolutions override is needed.
  • The patched release pulls in @humanfs/core@0.19.2 and the new @humanfs/types@0.15.0 dependency.

Verification

  • yarn why @humanfs/node reports only @humanfs/node@npm:0.16.8.
  • yarn workspace @sourcebot/web lint passes (eslint is the consumer of this package).
  • yarn test passes (2153 tests across queryLanguage, shared, backend, web).

🤖 Generated with Claude Code


Note

Low Risk
Lockfile-only transitive dependency security patch with no application code changes; impact is limited to ESLint’s filesystem layer during lint runs.

Overview
Bumps the transitive @humanfs/node dependency from 0.16.7 to 0.16.8 via a yarn.lock refresh (no package.json changes) to address GHSA-p498-v437-472g / SOU-2142, where recursive copy could follow symlinks and read files outside the source tree.

The resolved tree also moves to @humanfs/core@0.19.2 and adds @humanfs/types@0.15.0. eslint remains the consumer (^0.16.6 already allowed 0.16.8). The unreleased CHANGELOG records the upgrade.

Reviewed by Cursor Bugbot for commit 63ca585. Bugbot is set up for automated code reviews on this repo. Configure here.


Summary by cubic

Upgrades @humanfs/node to 0.16.8 in yarn.lock to fix SOU-2142 (GHSA-p498-v437-472g), where copy() and copyAll() followed symlinks and could read data from outside the source tree. This is a lockfile-only refresh; the existing ^0.16.6 range already permits the patched version, so no package.json change is needed.

  • Pulls in @humanfs/core@0.19.2 and adds @humanfs/types@0.15.0 as a new dependency.
  • Adds the upgrade to the unreleased CHANGELOG section.

Written for commit 63ca585. Summary will update on new commits.

Review in cubic

github-actions Bot and others added 2 commits September 4, 2026 12:27
Refreshes the yarn.lock entry for @humanfs/node (transitive via eslint)
from 0.16.7 to 0.16.8, which stops copy()/copyAll() from dereferencing
symlinks and copying files from outside the source tree. The existing
^0.16.6 range already admits the patched version, so no package.json
change is needed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

License Audit

⚠️ Status: PASS

Metric Count
Total packages 2174
Resolved (non-standard) 26
Unresolved 0
Strong copyleft 0
Weak copyleft 28

Weak Copyleft Packages (informational)

Package Version License
@img/sharp-libvips-darwin-arm64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-darwin-x64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linux-arm 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linux-arm64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linux-ppc64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linux-riscv64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linux-s390x 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linux-x64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linuxmusl-arm64 1.3.2 LGPL-3.0-or-later
@img/sharp-libvips-linuxmusl-x64 1.3.2 LGPL-3.0-or-later
@img/sharp-wasm32 0.35.3 Apache-2.0 AND LGPL-3.0-or-later AND MIT
@img/sharp-win32-arm64 0.35.3 Apache-2.0 AND LGPL-3.0-or-later
@img/sharp-win32-ia32 0.35.3 Apache-2.0 AND LGPL-3.0-or-later
@img/sharp-win32-x64 0.35.3 Apache-2.0 AND LGPL-3.0-or-later
axe-core 4.10.3 MPL-2.0
dompurify 3.4.13 (MPL-2.0 OR Apache-2.0)
lightningcss 1.32.0 MPL-2.0
lightningcss-android-arm64 1.32.0 MPL-2.0
lightningcss-darwin-arm64 1.32.0 MPL-2.0
lightningcss-darwin-x64 1.32.0 MPL-2.0
lightningcss-freebsd-x64 1.32.0 MPL-2.0
lightningcss-linux-arm-gnueabihf 1.32.0 MPL-2.0
lightningcss-linux-arm64-gnu 1.32.0 MPL-2.0
lightningcss-linux-arm64-musl 1.32.0 MPL-2.0
lightningcss-linux-x64-gnu 1.32.0 MPL-2.0
lightningcss-linux-x64-musl 1.32.0 MPL-2.0
lightningcss-win32-arm64-msvc 1.32.0 MPL-2.0
lightningcss-win32-x64-msvc 1.32.0 MPL-2.0
Resolved Packages (26)
Package Version Original Resolved Source
@sentry/cli 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-darwin 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-darwin 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-arm 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-arm 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-arm64 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-arm64 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-i686 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-i686 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-x64 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-linux-x64 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-win32-arm64 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-win32-arm64 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-win32-i686 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-win32-i686 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-win32-x64 2.58.5 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
@sentry/cli-win32-x64 2.58.6 FSL-1.1-MIT FSL-1.1-MIT npm registry metadata for the exact version + LICENSE file in the published tarball (Functional Source License 1.1, MIT Future License) + repo LICENSE at tag 2.58.x
codemirror-lang-elixir 4.0.0 UNKNOWN Apache-2.0 GitHub repo LICENSE (livebook-dev/codemirror-lang-elixir, Apache-2.0) + shipped LICENSE file; npm declares Apache-2.0 from v4.0.1 on
khroma 2.1.0 UNKNOWN MIT GitHub repo license file (fabiospampinato/khroma, detected MIT) + shipped license file (MIT text)
lezer-elixir 1.1.2 UNKNOWN Apache-2.0 GitHub repo LICENSE (livebook-dev/lezer-elixir, Apache-2.0) + shipped LICENSE file; npm declares Apache-2.0 from v1.1.3 on
map-stream 0.1.0 UNKNOWN MIT npm registry declares MIT for later versions + shipped LICENCE file (MIT text) + GitHub repo detected MIT
memorystream 0.3.1 UNKNOWN MIT extracted from object: legacy licenses array [{"type":"MIT",...}] in package.json/registry metadata; corroborated by shipped LICENSE file
pause-stream 0.0.11 ["MIT", "Apache2"] (MIT OR Apache-2.0) extracted from array-valued license field ["MIT","Apache2"]; shipped LICENSE file states "Dual Licensed MIT and Apache 2"
posthog-js 1.369.0 SEE LICENSE IN LICENSE (Apache-2.0 AND MIT) shipped LICENSE file (Apache-2.0 for the project, embedded MIT notices for vendored Mixpanel/Expo code); npm declares "(Apache-2.0 AND MIT)" for later versions
valid-url 1.0.9 UNKNOWN MIT shipped LICENSE file (verbatim MIT text); GitHub reports NOASSERTION only due to the non-standard copyright line

@brendan-kellam
brendan-kellam merged commit 09bbfe9 into main Sep 9, 2026
11 checks passed
@brendan-kellam
brendan-kellam deleted the cursor/cve/humanfs-node branch September 9, 2026 18:30
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