← Back
CVE-2026-49144
medium
CVSS 6.5
Path Traversal in browserstack-runner (CVE-2026-49144)
Summary
path traversal in browserstack-runner (CVE-2026-49144). Confidential information can be exposed externally. Exploitable via ``_default``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49144** has been found in browserstack-runner.
Attackers can target a specific entry point like ``_default`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "browserstack-runner CVE-2026-49144" on the vendor's site.
CVE-2026-49144 (browserstack-runner) — CWE-22 / CVSS v3 6.5
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: `_default` / `uri` / `path.join` / `username`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in browserstack-runner. Attackers reach the vulnerable code path via ``_default`` without authentication.
📍 Affected scope
browserstack-runner — . Attack surface: `_default` / `uri` / `path.join` / `username`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'browserstack-runner' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'browserstack-runner' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `browserstack-runner` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
browserstack-runner
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"0.9.5"}]}]