Skip to content

Add @n8n/task-runner to affected packages for GHSA-jjpj-p2wh-qf23 - #8971

Open
brittf619 wants to merge 1 commit into
github:brittf619/advisory-improvement-8971from
brittf619:ghsa-jjpj-p2wh-qf23-subpackage-attribution
Open

Add @n8n/task-runner to affected packages for GHSA-jjpj-p2wh-qf23#8971
brittf619 wants to merge 1 commit into
github:brittf619/advisory-improvement-8971from
brittf619:ghsa-jjpj-p2wh-qf23-subpackage-attribution

Conversation

@brittf619

Copy link
Copy Markdown

Summary

This advisory currently lists only the n8n umbrella package under affected. The vulnerable code — the JavaScript Task Runner sandbox — lives in @n8n/task-runner, which is published to npm as an independent scoped package. Downstream consumers of GHSA/OSV data (OSV.dev, NVD, dependency scanners) miss the sub-package attribution and undercount exposure when @n8n/task-runner is resolved without the umbrella package.

This attribution is especially relevant given the advisory's note that instances running external Task Runners (N8N_RUNNERS_MODE=external) run @n8n/task-runner as a standalone process, potentially decoupled from the umbrella n8n install.

The fixed versions differ from the umbrella n8n package (1.123.22 / 2.9.3 / 2.10.1) because @n8n/task-runner versions independently within the monorepo.

Verification

The @n8n/task-runner version at each umbrella fix tag was confirmed from packages/@n8n/task-runner/package.json in the n8n monorepo:

n8n@1.123.22 → @n8n/task-runner@1.59.16
n8n@2.9.3 → @n8n/task-runner@2.9.1
n8n@2.10.1 → @n8n/task-runner@2.10.1

Related PRs

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