Exposure of Sensitive Information in Jenkins Core
Jenkins before 1.650 and LTS before 1.642.2 do not use a constant-time algorithm to verify API tokens, which makes it easier for remote attackers to determine API tokens via a brute-force approach.
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 | < 1.650 | 1.650 |
References
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Weakness (CWE)
CWE-200- Platform
- Java / Kotlin (Maven)
- Package
org.jenkins-ci.main:jenkins-core- Disclosed
- 14.05.2022
- Updated
- 11.10.2026 11:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-jgpr-qrw2-6gp3 - 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
-
Exposure of Sensitive Information in Jenkins Core 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.