Observable timing discrepancy allows determining username validity in Jenkins
In Jenkins 2.355 and earlier, LTS 2.332.3 and earlier, an observable timing discrepancy on the login form allows distinguishing between login attempts with an invalid username, and login attempts with a valid username and wrong password, when using the Jenkins user database security realm. This allows attackers to determine the validity of attacker-specified usernames.
Login attempts with an invalid username now validate a synthetic password to eliminate the timing discrepancy in Jenkins 2.356, LTS 2.332.4.
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.334, < 2.356, < 2.332.4 | 2.356, 2.332.4 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Weakness (CWE)
CWE-203, CWE-208- Platform
- Java / Kotlin (Maven)
- Package
org.jenkins-ci.main:jenkins-core- Disclosed
- 24.06.2022
- Updated
- 11.10.2026 11:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-9grj-j43m-mjqr - 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
-
Observable timing discrepancy allows determining username validity 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.