Cross-Site Request Forgery in Jenkins
A race condition during Jenkins 2.94 and earlier; 2.89.1 and earlier startup could result in the wrong order of execution of commands during initialization. There is a very short window of time after startup during which Jenkins may no longer show the 'Please wait while Jenkins is getting ready to work' message but Cross-Site Request Forgery (CSRF) protection may not yet be effective.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.jenkins-ci.main:jenkins-core | >= 2.81, < 2.89.2, >= 2.90, < 2.95 | 2.89.2, 2.95 |
References
- CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-352- Platform
- Java / Kotlin (Maven)
- Package
org.jenkins-ci.main:jenkins-core- Disclosed
- 14.05.2022
- Updated
- 11.10.2026 12:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-99hj-ppg3-2xwc - CC BY 4.0
Vulnerability history: org.jenkins-ci.main:jenkins-core
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 259
- First → latest
- 01.2022 06.2026
- Without a fix
- 1
- Exploited in attacks
- 4
Severity breakdown
- Critical 19
- High 62
- Medium 158
- Low 20
Disclosures per year
- 2022: 213
- 2023: 14
- 2024: 6
- 2025: 14
- 2026: 12
-
Cross-Site Request Forgery in Jenkins this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.