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

Cross-Site Request Forgery in Vert.x-Web frameworkGHSA-9q69-g5gc-9fgf

HIGHFix: vert-x3/vertx-web#1613

GHSA-9q69-g5gc-9fgf is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in io.vertx:vertx-web. A fix is available for io.vertx:vertx-web — see the affected versions and patch details below.

Also known asCVE-2020-35217
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk
0.00%0.36%0.72%1.09%0.2%0.6%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

4 pkgs affected
☕io.vertx:vertx-web☕io.vertx:vertx-web☕io.vertx:vertx-web☕io.vertx:vertx-web

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

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.vertx:vertx-web≥ 4.0.0-milestone1&&< 4.0.0-milestone54.0.0-milestone5io.vertx:vertx-web:4.0.0-milestone5
☕Mavenio.vertx:vertx-web≥ 4.0.0-milestone2&&< 4.0.0-milestone54.0.0-milestone5io.vertx:vertx-web:4.0.0-milestone5
☕Mavenio.vertx:vertx-web≥ 4.0.0-milestone3&&< 4.0.0-milestone54.0.0-milestone5io.vertx:vertx-web:4.0.0-milestone5
☕Mavenio.vertx:vertx-web≥ 4.0.0-milestone4&&< 4.0.0-milestone54.0.0-milestone5io.vertx:vertx-web:4.0.0-milestone5

Affected Products

1 product · 4 configurations
Application
vert.x-webeclipse
1 version
4.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update io.vertx:vertx-web to 4.0.0-milestone5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q69-g5gc-9fgf 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.

Frequently Asked Questions

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.
O3 Security · Impact-Aware SCA

Is GHSA-9q69-g5gc-9fgf in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Cross-Site Request Forgery in Vert.x-Web framework