Skip to content

[GHSA-gp2j-mg4w-2rh5] chrome-launcher subject to OS Command Injection#7487

Closed
Wenxin-Jiang wants to merge 1 commit intoWenxin-Jiang/advisory-improvement-7487from
Wenxin-Jiang-GHSA-gp2j-mg4w-2rh5
Closed

[GHSA-gp2j-mg4w-2rh5] chrome-launcher subject to OS Command Injection#7487
Wenxin-Jiang wants to merge 1 commit intoWenxin-Jiang/advisory-improvement-7487from
Wenxin-Jiang-GHSA-gp2j-mg4w-2rh5

Conversation

@Wenxin-Jiang
Copy link
Copy Markdown

Updates

  • Affected products
  • Description

Comments
The advisory currently marks chrome-launcher@0.10.6 as affected across the range >= 0.0.0 < 0.13.2. However, the published npm tarball for 0.10.6 is a broken release: it includes neither the compiled dist/ output nor the TypeScript src/ sources. As a result, the vulnerable module—chrome-finder.{js,ts}, which contains findChromeExecutables—is not present in the shipped artifact.

Because that code is absent, the vulnerable path is not reachable in the installed package and cannot be recreated from the published contents. There are no sources for tsc to compile, and require('chrome-launcher') fails with ERR_MODULE_NOT_FOUND before any launcher logic executes.

@github-actions github-actions Bot changed the base branch from main to Wenxin-Jiang/advisory-improvement-7487 April 22, 2026 19:36
@helixplant helixplant closed this Apr 22, 2026
@github-actions github-actions Bot deleted the Wenxin-Jiang-GHSA-gp2j-mg4w-2rh5 branch April 22, 2026 19:56
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.

2 participants