Security readout for executives and security teams
Plain-English summary
A malicious Git repository or branch name can make vulnerable WebdriverIO BrowserStack test orchestration execute unintended operating-system commands. CI/CD servers and developer machines are most at risk, where compromise could expose credentials, alter source or build artifacts, and disrupt systems. WebdriverIO fixed the issue in version 9.24.0.
Executive priority
Treat this as an immediate remediation for internet-facing or externally contributed CI workflows. Prioritize systems where test jobs can access production credentials, signing keys, deployment tokens, or sensitive source code. Less-exposed environments still require prompt inventory and upgrade because compromise could become a software supply-chain incident.
Technical view
WebdriverIO versions below 9.24.0 contain a CWE-78 command-injection flaw in the BrowserStack service. getGitMetadataForAISelection() places Git branch names into execSync() shell commands without sanitization. When test orchestration processes an attacker-controlled repository, shell metacharacters in repository metadata can produce arbitrary code execution under the test process account.
Likely exposure
Exposure is highest where WebdriverIO BrowserStack test orchestration processes untrusted repositories or attacker-influenced branches, including pull-request and external-source CI workflows. The vulnerable repository may be supplied through runSmartSelection.source or taken from the current directory. Deployments not using the affected service or workflow may not be reachable, but versions must still be inventoried.
Exploitation context
The source bundle does not report observed active exploitation, and its KEV flag is false. Exploitation nevertheless has severe potential because affected test jobs may hold source access, signing material, cloud credentials, tokens, or deployment permissions. Actual reach depends on whether an attacker can control repository metadata processed by the vulnerable workflow.
Researcher notes
The vulnerable trust boundary is Git metadata entering shell execution during AI-selection metadata collection. The supplied CVSS 3.1 score is 9.8, with no privileges or user interaction indicated. Researchers should distinguish package presence from reachability by confirming BrowserStack test orchestration, smart-selection execution, repository provenance, and the privileges of the invoking process.
Mitigation direction
- Upgrade affected WebdriverIO installations to version 9.24.0 or later.
- Until upgraded, prevent BrowserStack smart-selection workflows from processing untrusted repositories or branches.
- Restrict CI/CD credentials and permissions to the minimum required for each test job.
- Rotate exposed secrets if vulnerable jobs processed attacker-controlled repository metadata.
- Rebuild and verify artifacts produced by any potentially compromised pipeline.
Validation and detection
- Inspect manifests and lockfiles for WebdriverIO versions below 9.24.0.
- Determine whether the BrowserStack service and test-orchestration smart selection are enabled.
- Identify workflows that accept external repositories, forks, pull requests, or attacker-influenced branch names.
- Review relevant job logs and endpoint telemetry for unexpected child processes or secret access.
- Confirm deployed dependencies resolve to version 9.24.0 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-25244 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H2.15.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-18T21:01:56.919Z: Reported to Red Hat.
- 2026-05-18T20:31:14.497Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/webdriverio/webdriverio/security/advisories/GHSA-5c46-x3qw-q7j7CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/webdriverio/webdriverio/blob/ea0e3e00288abced4c739ff9e46c46977b7cdbd2/packages/wdio-browserstack-service/src/testorchestration/helpers.ts#L204CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/webdriverio/webdriverio/releases/tag/v9.24.0CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-25244CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2479692CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25244.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.