NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2022-28108 — selenium-grid

HIGH

CVE-2022-28108 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in org.seleniumhq.selenium:selenium-grid. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.seleniumhq.selenium:selenium-grid — see the affected versions and patch details below.

Selenium Server (Grid) CSRF

Also known asGHSA-h2rr-m97p-6jq9PYSEC-2022-43167
Published
Updated
Affected
2 pkgs
Patched
1 / 2
Exploits
3 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
22.5%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk
8.48%14.3%20.0%25.8%22.4%22.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.seleniumhq.selenium:selenium-grid☕org.seleniumhq.selenium:selenium-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Selenium Server (Grid) before 4 allows CSRF because it permits non-JSON content types such as application/x-www-form-urlencoded, multipart/form-data, and text/plain.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.seleniumhq.selenium:selenium-gridall versions4.0.0-alpha-7org.seleniumhq.selenium:selenium-grid:4.0.0-alpha-7
☕Mavenorg.seleniumhq.selenium:selenium-serverall versionsNo fix

Affected Products

1 product · 8 configurations
Application
selenium gridselenium
< 4.0.0
1 version
4.0.0
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.seleniumhq.selenium:selenium-grid, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.seleniumhq.selenium:selenium-grid to 4.0.0-alpha-7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-28108 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2022-28108

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2022-28108 -u https://target
Template
Selenium Grid < 4.0.0-alpha-7 - Remote Code Execution
Severity
critical
Impact
An unauthenticated attacker can achieve remote code execution as the Selenium Grid process owner by crafting a malicious payload and sending it to the /wd/hub/session endpoint.
Remediation
Upgrade to Selenium Server 4.0.0-alpha-7 or later and restrict network exposure.

Template by ProjectDiscovery nuclei-templates (t0xk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Selenium Server (Grid) before 4 allows CSRF because it permits non-JSON content types such as application/x-www-form-urlencoded, multipart/form-data, and text/plain.
O3 Security · Impact-Aware SCA

Is CVE-2022-28108 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2022-28108: selenium-grid CSRF — Fix Available