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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g4w6-c99w-4wh7 can be triaged on real exposure rather than presence alone.

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 is the EPSS score for GHSA-g4w6-c99w-4wh7?

GHSA-g4w6-c99w-4wh7 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Not in CISA KEV

GHSA-g4w6-c99w-4wh7 — browserstack-local

GHSA-g4w6-c99w-4wh7 is a Code Injection vulnerability in browserstack-local. A fix is available for browserstack-local — see the affected versions and patch details below.

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

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-g4w6-c99w-4wh7.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

88other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

browserstack-localnpm

764Kdownloads / 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`npm install browserstack-local@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g4w6-c99w-4wh7 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-g4w6-c99w-4wh7 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works