How severe is GHSA-g4w6-c99w-4wh7?

No CVSS score has been assigned to GHSA-g4w6-c99w-4wh7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g4w6-c99w-4wh7?

GHSA-g4w6-c99w-4wh7 affects the following packages: browserstack-local (npm). Ecosystems affected: npm.

How do I fix GHSA-g4w6-c99w-4wh7?

Update browserstack-local to 1.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4w6-c99w-4wh7 is resolved across your whole dependency graph.

How do I detect GHSA-g4w6-c99w-4wh7 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for browserstack-local. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g4w6-c99w-4wh7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g4w6-c99w-4wh7?

O3 pinpoints whether GHSA-g4w6-c99w-4wh7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g4w6-c99w-4wh7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-g4w6-c99w-4wh7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-g4w6-c99w-4wh7?

GHSA-g4w6-c99w-4wh7 is classified as Code Injection (CWE-94), OS Command Injection (CWE-78). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-g4w6-c99w-4wh7 published, and has it been updated?

GHSA-g4w6-c99w-4wh7 was published on January 28, 2026 and was last updated on February 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-g4w6-c99w-4wh7

GHSA-g4w6-c99w-4wh7 is a Code Injection vulnerability in browserstack-local. O3 Security confirms whether GHSA-g4w6-c99w-4wh7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

BrowserStack Local vulnerable to Command Injection through logfile variable

Also known asCVE-2025-57283

Published

Jan 28, 2026

Updated

Feb 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

browserstack-localnpm

825Kdownloads / week

Description

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`browserstack-local`	all versions	1.5.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for browserstack-local. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update browserstack-local to 1.5.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4w6-c99w-4wh7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-g4w6-c99w-4wh7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g4w6-c99w-4wh7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The Node.js package browserstack-local 1.5.8 contains a command injection vulnerability. This occurs because the logfile variable is not properly sanitized in lib/Local.js.

O3 Security · Impact-Aware SCA

Is GHSA-g4w6-c99w-4wh7 in your dependencies?

O3 detects GHSA-g4w6-c99w-4wh7 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works