Repository navigation
Conversation
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>
✅ Deploy Preview for flashlight-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This branch has not been deployed
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
Fixes Dependabot alert GHSA-85c8-ppgw-ccpr (CVE-2026-104849, critical): in
tinypool< 2.1.2,pool.run(task, options)readsfilenamethrough the prototype chain. IfObject.prototypehas 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/core3.10.2 is already the latest release and still declarestinypool: ^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
resolutionsentry"tinypool": "^2.1.2"inwebsite/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 rootpackage.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:
pool.run(task)with no options object, and the advisory says that form is not affected.docusaurus.config.jsdoesn't turn onfuture.faster.ssgWorkerThreads, so tinypool is never imported.Evidence
yarn why tinypoolinwebsite/, before (lockfile onmain):after:
Compatibility with Docusaurus:
process.__tinypool_state__that Docusaurus's SSG worker reads.future.faster.ssgWorkerThreads: trueand ranyarn buildinwebsite/. 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 testfrom the root: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.2range 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 withclaude --resume d594597f-18e1-42d1-8666-6925d88a98de.🤖 Generated with Claude Code