gatling vulnerabilities and fixes
Recent CVEs affecting gatling, with upgrade or downgrade steps. 3 tracked.
gatling has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2025-08-06. Highest priority: CVE-2025-51306 (score 42/100).
- CVE-2025-5806 HIGH 8.0 UPGRADE Jenkins Gatling Plugin 136.vb_9009b_3d33a_e serves Gatling reports in a manner that bypasses the Content-Secur
- CVE-2025-51308 MEDIUM 5.3 UPGRADE In Gatling Enterprise versions below 1.25.0, a low-privileged user that does not hold the role "admin" could p
- CVE-2025-51306 MEDIUM 6.5 UPGRADE In Gatling Enterprise versions below 1.25.0, a user logging-out can still use his session token to continue us
FAQ
How do I fix gatling vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is gatling being exploited right now?
None of the tracked gatling CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gatling CVE should I patch first?
CVE-2025-51306 currently ranks highest (42/100): In Gatling Enterprise versions below 1.25.0, a user logging-out can still use his session token to continue us.