View name validation bypass in Jenkins
Jenkins 2.286 and earlier, LTS 2.277.1 and earlier does not properly check that a newly created view has an allowed name. When a form to create a view is submitted, the name is included twice in the submission. One instance is validated, but the other instance is used to create the value.
This allows attackers with View/Create permission to create views with invalid or already-used names.
Jenkins 2.287, LTS 2.277.2 uses the same submitted value for validation and view creation.
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.277.2, >= 2.278, < 2.287 | 2.277.2, 2.287 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N- Weakness (CWE)
CWE-240- Platform
- Java / Kotlin (Maven)
- Package
org.jenkins-ci.main:jenkins-core- Disclosed
- 24.05.2022
- Updated
- 11.10.2026 11:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-w2hv-rcqr-2h7r - 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
-
View name validation bypass 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.