dbcve.org
WebdriverioApplication · Openjsf

CVE-2026-25244

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-18
Fix available
A fix is available. Upgrade to 9.24.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
WebdriverIO is a test automation framework for unit, e2e and component testing using WebDriver, WebDriver BiDi and Appium. Versions below 9.24.0 contain a command injection vulnerability leading to remote code execution (RCE) in test orchestration. Git permits branch names containing shell metacharacters, and getGitMetadataForAISelection() interpolates these names directly into execSync() calls without sanitization. An attacker can exploit this by supplying a malicious repository (via testOrchestrationOptions.runSmartSelection.source, or the current directory if unset) whose branch name carries a payload, causing the shell to execute arbitrary code. This enables remote code execution on CI/CD servers and developer machines, leading to credential and secret disclosure, source code and SSH key exfiltration, system compromise, and supply chain attacks via tampered build artifacts. The issue has been fixed in version 9.24.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WebdriverIO versions below 9.24.0 have a command injection vulnerability in the getGitMetadataForAISelection() function. This function directly interpolates Git branch names into execSync() calls without sanitization, allowing attackers to inject shell commands via malicious branch names in test orchestration options.

MitigationUpgrade to WebdriverIO version 9.24.0 or later. If immediate upgrade is not feasible, implement input sanitization for branch names before they are passed to execSync() calls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WebdriverioApplication
Affected:< 9.24.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed WebdriverIO version
    Run 'npm list webdriverio' or 'yarn list webdriverio' in your project directory, or check package.json for the webdriverio dependency version
    Affected if The installed version is below 9.24.0 (e.g., 9.23.0, 9.0.0, etc.)
  2. Verify getGitMetadataForAISelection is in use
    Search your codebase for references to 'getGitMetadataForAISelection' function call - look in your project's JavaScript/TypeScript files and node_modules for this function name
    Affected if Your codebase or dependencies call getGitMetadataForAISelection and the version is below 9.24.0
  3. Confirm git is used in the application
    Check if your project uses git commands or the WebdriverIO git integration features - look for .git directory, git config, or code that interacts with git repositories
    Affected if Git is integrated and the vulnerable function can be triggered with branch names passed to git commands
  4. Review branch name inputs
    Inspect any code paths where user-controlled or external branch names are passed to WebdriverIO git metadata functions - check if branch names could contain shell metacharacters like ; | $ ` or other command injection payloads
    Affected if Branch names from users or external sources are passed without sanitization to git operations in WebdriverIO below 9.24.0

You are affected if WebdriverIO version is below 9.24.0 AND your application uses the getGitMetadataForAISelection function with branch names that could contain shell metacharacters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.24.0 or later
Fixed in 9.24.0
Interim mitigation

Upgrade to WebdriverIO version 9.24.0 or later. If immediate upgrade is not feasible, implement input sanitization for branch names before they are passed to execSync() calls.

Recommended fix High confidence

9.24.0

  1. Upgrade WebdriverIO to version 9.24.0 or later by running: npm install [email protected] or npm install webdriverio@latest
  2. Verify the upgrade was successful by checking the installed version: npm list webdriverio
  3. Test your test suite to ensure functionality remains intact after the upgrade
Caveat Review WebdriverIO 9.24.0 release notes for any potential breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webdriverio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25244 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data