Skip to content

fix(deps): bump tinypool to 2.2.0 in website (GHSA-85c8-ppgw-ccpr) - #415

Draft
AlecColas wants to merge 1 commit into
mainfrom
factory/20261117-093225-fix-cve-flashlight-206
Draft

AlecColas wants to merge 1 commit into
mainfrom
factory/20261117-093225-fix-cve-flashlight-206

Conversation

@AlecColas

Copy link
Copy Markdown
Contributor

Summary

Fixes Dependabot alert GHSA-85c8-ppgw-ccpr (CVE-2026-104849, critical): in tinypool < 2.1.2, pool.run(task, options) reads filename through the prototype chain. If Object.prototype has been polluted, tinypool can load a worker module chosen by an attacker.

Why it's installed: only in the docs site (website/yarn.lock), as a dependency of @docusaurus/core, which uses it for multi-threaded static-site generation (SSG). @docusaurus/core 3.10.2 is already the latest release and still declares tinypool: ^1.0.2. No patched 1.x release exists (the fix landed in 2.1.2), so bumping the parent does not help.

What changed: a resolutions entry "tinypool": "^2.1.2" in website/package.json. The website has its own lockfile and is not part of the root workspace, so the entry goes there rather than in the root package.json. The lockfile diff only changes the tinypool entry (1.1.1 → 2.2.0). Remove the resolution once Docusaurus depends on tinypool ^2.

The site was not exploitable in practice:

  • Docusaurus calls pool.run(task) with no options object, and the advisory says that form is not affected.
  • docusaurus.config.js doesn't turn on future.faster.ssgWorkerThreads, so tinypool is never imported.

Evidence

yarn why tinypool in website/, before (lockfile on main):

tinypool@^1.0.2:
  version "1.1.1"

after:

info => Found "tinypool@2.2.0"
info Reasons this module exists
   - "@docusaurus#core" depends on it
   - Hoisted from "@docusaurus#core#tinypool"

Compatibility with Docusaurus:

  • tinypool 2.x keeps the same ESM entry and still sets the process.__tinypool_state__ that Docusaurus's SSG worker reads.
  • The only breaking change in 2.0 is dropping Node 18. Netlify builds on Node 22.
  • I temporarily set future.faster.ssgWorkerThreads: true and ran yarn build in website/. This forces the tinypool-pooled SSG path on 2.2.0. All pages were generated ([SUCCESS] Generated static files in "build".). The config change was reverted before committing.

yarn test from the root:

All matched files use Prettier code style!
Test Suites: 22 passed, 22 total
Tests:       60 passed, 60 total
Snapshots:   22 passed, 22 total
Done in 446.20s.

Merge risk

Low. Only the docs site build is affected; the published @perf-profiler/* packages are not. The resolution takes tinypool past the ^1.0.2 range Docusaurus declares, but tinypool is not imported with the current config, and the pooled path was checked by hand. Netlify's deploy preview will confirm the production build.

🤖 Generated with Claude Code


Opened by the Flashlight AI factory (run 20261117-093225-fix-cve-flashlight-206). Take over locally with claude --resume d594597f-18e1-42d1-8666-6925d88a98de.

🤖 Generated with Claude Code

Docusaurus 3.10.2 (latest) still declares tinypool ^1.0.2 and no 1.x
release is patched, so force it with a resolutions entry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@netlify

netlify Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for flashlight-docs ready!

Name Link
🔨 Latest commit 96de9ce
🔍 Latest deploy log https://app.netlify.com/projects/flashlight-docs/deploys/6afc15634538c286eebe2a19
😎 Deploy Preview https://deploy-preview-415--flashlight-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

This branch has not been deployed

No deployments
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