Repository navigation
chore(deps): update dependency @wdio/browserstack-service to v9 [security] - autoclosed - #1001
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
renovate
Bot
deleted the
renovate/npm-wdio-browserstack-service-vulnerability
branch
August 12, 2026 21:56
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
2 times, most recently
from
August 14, 2026 20:43
eaa236a to
268d20b
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
from
August 26, 2026 18:11
268d20b to
8f1f2a4
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
4 times, most recently
from
September 8, 2026 00:34
6d567ff to
9c0c753
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
3 times, most recently
from
September 15, 2026 15:49
e07832b to
0fd50b1
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
2 times, most recently
from
September 24, 2026 17:06
9a9e5b7 to
81fbafb
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
2 times, most recently
from
October 5, 2026 15:29
c1efaea to
ca96eda
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
from
October 13, 2026 16:40
ca96eda to
cd1845d
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
from
October 21, 2026 17:05
e39701a to
cd1845d
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
2 times, most recently
from
October 26, 2026 21:50
e39701a to
5325c15
Compare
renovate
Bot
force-pushed
the
renovate/npm-wdio-browserstack-service-vulnerability
branch
2 times, most recently
from
October 30, 2026 11:17
5325c15 to
caa1ae3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
8.40.6→9.24.0WebdriverIO BrowserStack Service has a Command Injection issue
CVE-2026-25244 / GHSA-5c46-x3qw-q7j7
More information
Details
Summary
A command injection vulnerability exists in
@wdio/browserstack-servicethat allows remote code execution (RCE) when processing git branch names in test orchestration. An attacker can exploit this by providing a malicious git repository with a branch name containing shell command injection payloads.Details
Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer.
Vulnerable Code
File: https://github.com/webdriverio/webdriverio/blob/ea0e3e00288abced4c739ff9e46c46977b7cdbd2/packages/wdio-browserstack-service/src/testorchestration/helpers.ts#L204
Root Cause
User-controlled git branch names are directly interpolated into
execSync()calls without sanitization. Git allows branch names to contain special characters ,that can be used for command injection.Git allows to create these branches.
Attack Vector
testOrchestrationOptions.runSmartSelection.source. ifsourceis not provided it takes current directory assource.getGitMetadataForAISelection()executes, it extracts the malicious branch namePoC
Step 1: Create Malicious Repository Branch
Step 2: Configure WebdriverIO
Step 3: Run Tests
Step 4: Verify RCE
##### Check if file was created (proof of RCE) ls -la /tmp/pwned.txtImpact
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
browserstack/wdio-browserstack-service (@wdio/browserstack-service)
v9.24.0Compare Source
v9.23.3Compare Source
v9.23.2Compare Source
v9.23.1Compare Source
v9.23.0Compare Source
v9.22.0Compare Source
v9.21.0Compare Source
v9.20.1Compare Source
v9.20.0Compare Source
v9.19.2Compare Source
v9.19.1Compare Source
v9.19.0Compare Source
v9.18.4Compare Source
v9.18.3Compare Source
v9.18.1Compare Source
v9.18.0Compare Source
v9.17.0Compare Source
v9.16.2Compare Source
v9.16.1Compare Source
v9.16.0Compare Source
v9.15.0Compare Source
v9.14.0Compare Source
v9.13.0Compare Source
v9.12.7Compare Source
v9.12.6Compare Source
v9.12.5Compare Source
v9.12.4Compare Source
v9.12.3Compare Source
v9.12.2Compare Source
v9.12.1Compare Source
v9.12.0Compare Source
v9.11.0Compare Source
v9.10.1Compare Source
v9.10.0Compare Source
v9.9.3Compare Source
v9.9.2Compare Source
v9.9.1Compare Source
v9.9.0Compare Source
v9.8.0Compare Source
v9.7.3Compare Source
v9.7.2Compare Source
v9.7.1Compare Source
v9.7.0Compare Source
v9.6.4Compare Source
v9.6.3Compare Source
v9.6.2Compare Source
v9.6.1Compare Source
v9.6.0Compare Source
v9.5.7Compare Source
v9.5.6Compare Source
v9.5.4Compare Source
v9.5.3Compare Source
v9.5.2Compare Source
v9.5.1Compare Source
v9.5.0Compare Source
v9.4.5Compare Source
v9.4.4Compare Source
v9.4.3Compare Source
v9.4.2Compare Source
v9.4.1Compare Source
v9.4.0Compare Source
v9.3.1Compare Source
v9.3.0Compare Source
v9.2.14Compare Source
v9.2.12Compare Source
v9.2.11Compare Source
v9.2.8Compare Source
v9.2.6Compare Source
v9.2.5Compare Source
v9.2.4Compare Source
v9.2.2Compare Source
v9.2.1Compare Source
v9.2.0Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
v9.1.3Compare Source
v9.1.2Compare Source
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.9Compare Source
v9.0.8Compare Source
v9.0.7Compare Source
v9.0.6Compare Source
v9.0.5Compare Source
v9.0.4Compare Source
v9.0.2Compare Source
v9.0.1Compare Source
v9.0.0Compare Source
v8.55.2Compare Source
Patch Changes
3d8ba8c: - Removed the deprecated client-side self-healing extension. Self-healing on BrowserStack continues to work unchanged via thebrowserstack.selfHealcapability.v8.55.1Compare Source
Patch Changes
6fbcf41: - Fixed builds being reported as timed out on Test Reporting & Analytics when a Mochabefore/beforeEach/afterEachhook is declared outside anydescribeblock.v8.55.0Compare Source
Minor Changes
4d0de76: - Server-side configuration overrides from BrowserStack now take effect for WebdriverIO v8 builds, for exampleparallelsPerPlatform(parallel sessions per capability). Your wdio.conf remains the fallback.v8.54.0Compare Source
Minor Changes
8ff1b20: -testManagementOptionsset in the BrowserStack service options is now forwarded in full, soissuesandissueTrackercan link Jira issues to the build. The same JSON can be passed with theBROWSERSTACK_TEST_MANAGEMENT_OPTIONSenvironment variable or the--browserstack.testManagementOptionsCLI argument (Mocha and Cucumber).v8.53.3Compare Source
Patch Changes
c8c2933: - FixedBROWSERSTACK_PROJECT_NAMEandBROWSERSTACK_BUILD_NAMEbeing ignored — the environment now takes precedence over the project and build names in your config file, matching the other BrowserStack SDKs.v8.53.2Compare Source
Patch Changes
ccb370d: - SDK-6948:*.bsstag.comhubs are now recognised as BrowserStack on named internal staging envs (BROWSERSTACK_STAGING_ENV/BROWSERSTACK_ENV), so with the CLI flow (default) session marking and TRA linking work there. The classic (non-CLI) flow on a named staging env is not supported; its session update is skipped at debug.update_clifailures fall back toBROWSERSTACK_BINARY_URL. A failed fallback download uses the cached binary._printSessionURLand_updatelog a failed session lookup or update (HTTP error) at debug instead of throwing.25529d2: fix(cli): fall back toBROWSERSTACK_BINARY_URLwhenupdate_clifails (SDK-6948)update_cliruns during bootstrap — before the binary is spawned and before GRR localizes the API hosts — so it always targets productionapi.browserstack.com. On an internal staging run (BROWSERSTACK_STAGING_ENV) the staging credentials are rejected there (401), which left the CLI binary path empty and crashed the launcher withspawn('') … ERR_INVALID_ARG_VALUE: 'file' cannot be empty. Whenupdate_clifails andBROWSERSTACK_BINARY_URLis set, download the binary from that URL instead so the run can proceed; the same applies when a 2xx reply carries no download URL and no binary is cached. If that download fails, the cached binary is used when there is one, and both errors are logged. Opt-in only — with the variable unset the original error propagates exactly as before. Ports main/v9 #224 to the v8 line.7ef36e1: fix(util): recognize*.bsstag.comhosts as BrowserStack on internal staging envs (SDK-6948)getCloudProviderandisBrowserstackInfraonly matchedbrowserstack.com, so a session pointed at an internal staging env (*.bsstag.com) was classified as non-BrowserStack: session marking and Automate <-> TRA session linking did not work there.*.bsstag.comhosts are now treated as BrowserStack whenBROWSERSTACK_STAGING_ENVis a bare env name (e.g.k8s, trimmed; blank means unset) orBROWSERSTACK_ENVisstaging/stag/preprod/pre-prod. Hosts are matched case-insensitively. Production behaviour is unchanged. With the CLI flow (the default), session marking and Automate <-> TRA session linking now work on those envs, because the binary supplies the staging session REST host. The classic (non-CLI) flow on a named staging env is not supported: it has no staging session REST host, so the session name/status update is skipped at debug instead of failing the hook._printSessionURLand_updatelog a failed session lookup or update (HTTP error reply) at debug instead of throwing. Ports main/v9 #275 to the v8 line.v8.53.1Compare Source
Patch Changes
3cb779e: - Fixed custom test metadata set viaBrowserStackSDK.setTestMetadata()being dropped when the metadata is set before the test-run UUID is assigned. A per-UUID lookup now falls back to the current-run metadata again, restoring the behaviour that shipped before 8.51.0.4a49c07: - Fixed a configuredbuildIdentifierbeing dropped from the build name whenBROWSERSTACK_BUILD_NAMEwas set via environment variable.BROWSERSTACK_BUILD_RUN_IDENTIFIERandBROWSERSTACK_BUILD_IDENTIFIERare now honoured as build-identifier overrides.${CUSTOM_DATE}inbuildIdentifierare now substituted from the environment.9fc22b2: - Fixed custom test metadata set viaBrowserStackSDK.setTestMetadata()before the test-run UUID is assigned being dropped for App Low-Code runs.v8.53.0Compare Source
Minor Changes
7e631ec: - Cucumber tests on WebdriverIO now report through the BrowserStack CLI, matching the behaviour of Mocha.sessionNameFormatbeing ignored, so custom session names now apply on the CLI flow.Patch Changes
6736a40: - Fixed Percy visual testing on WebdriverIO: screenshots (Percy on Automate) and web snapshots are captured again. No config or code changes needed.v8.52.0Compare Source
Minor Changes
5b04b27: - End-of-build messages from BrowserStack — such as a notice that your SDK version is outdated or has a known issue — are now shown at the end of your test run, highlighted in yellow for a warning and red for an error, and written to the SDK log without colour so they stay searchable.v8.51.1Compare Source
Patch Changes
2443f4d: - Fixed accessibility command wrapping aborting on App Automate sessions, which loggedError in onBeforeExecuteand left the remaining commands unwrapped for auto-scanning. Applies to both the CLI and the non-CLI flow.5dcf7b8: - Fixed test tags not being reported to Test Observability for Mocha and Jasmine. Tags written as@tagtokens in suite or test titles are now sent with each test.f03908b: - N/A — CI/workflow-only change; no customer-facing or package impact.0966598: ci(sdk-pr-review-gate): thegaterequired check now turns green as soon as the SDK PR Review Agent has run on the PR's latest commit (any verdict), not only when it passes — verdict is advisory. Rolls the mandatory-to-run gate change (SDK-7256) onto the v8 line; main already has it via #202.v8.51.0Compare Source
Minor Changes
650c514: - Added support for attaching custom test metadata to test runs viaBrowserStackSDK.setTestMetadata()for central-user integrations.v8.50.0Compare Source
Minor Changes
635fc26: Added support for the skipAppOverride flag.[
v8.49.2](https://redirect.github.com/browserstack/wdio-browserstack-service/releases/tag/%40wdio/broConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.