ChromeDriver
Overview
CPE
cpe:2.3:a:chromium:chromedriver Version & Lifecycle
Community Notes
ChromeDriver portable deployment and version-matching note
ChromeDriver is distributed as a portable executable/ZIP, so normal Windows silent-install switches do not apply. For enterprise test hosts, script the download, extract chromedriver.exe to a controlled location such as C:\WebDriver\bin, and reference that full path from Selenium/WebDriver jobs instead of expecting an MSI-style install.
For Chrome 115 and newer, use Google’s Chrome for Testing availability data or dashboard to select matching Chrome and ChromeDriver artifacts. Pin the driver version to the Chrome channel/build you deploy to automation hosts; otherwise browser auto-update can leave test agents with a Chrome/ChromeDriver mismatch.
For legacy Chrome 114 and older, Google’s ChromeDriver downloads page still points to the older version-selection flow. Keep that distinction in packaging scripts so old long-lived lab images do not accidentally consume the new Chrome for Testing JSON endpoint while current images do.
Official Google sources: ChromeDriver downloads/version selection and Chrome for Testing availability dashboard.
Release Notes & Updates
Known Vulnerabilities
None found.
No published CVEs against
cpe:2.3:a:chromium:chromedriver.
Looks wrong? Suggest a different match
Don’t see it? Paste a CPE
Also known as
Other names people use for this app — helps search and matching.
Sign in to suggest a name.
Packaging Notes
Distributed as a standalone executable zip archive; often managed via Selenium Manager or package managers
