chromedriver Command Injection vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-26156: 2.23% estimated exploitation activity in the next 30 days; percentile 82.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Versions of the package chromedriver before 119.0.1 are vulnerable to Command Injection when setting the chromedriver.path to an arbitrary system binary. This could lead to unauthorized access and potentially malicious actions on the host system. Note: An attacker must have access to the system running the vulnerable chromedriver library to exploit it. The success of exploitation also depends on the permissions and privileges of the process running chromedriver.

Published by the source

9 Nov 2023, 06:30 UTC

Last modified by the source

17 Nov 2023, 22:12 UTC

Source last checked

26 Oct 2026, 12:29 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-hm92-vgmw-qfmx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-hm92-vgmw-qfmx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-26156

Advisory: chromedriver Command Injection vulnerability
IDs: CVE-2023-26156, GHSA-hm92-vgmw-qfmx
Record: https://patchnext.com/advisories/cve-2023-26156 (revision 2, source checked 26 Oct 2026, 12:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: chromedriver 119.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm chromedriver: affected < 119.0.1; fixed in 119.0.1

## Suggested inspection (read-only)
- `npm ls chromedriver --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on chromedriver.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hm92-vgmw-qfmx (OSV record GHSA-hm92-vgmw-qfmx lists affected ranges: npm chromedriver >=0 <119.0.1 (fixed))
- Verified: https://github.com/advisories/GHSA-hm92-vgmw-qfmx (GitHub-reviewed advisory GHSA-hm92-vgmw-qfmx lists affected ranges: npm chromedriver >=0 <119.0.1)

Commands are suggestions: review each one before running it.