Jenkins improperly ensures trust separation
Jenkins prior to 1.587 and LTS before 1.580.1 do not properly ensure trust separation between a master and slaves, which might allow remote attackers to execute arbitrary code on the master by leveraging access to the slave.
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.587 | 1.587 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2014-3665
- https://access.redhat.com/errata/RHBA-2014:1630
- https://access.redhat.com/security/cve/CVE-2014-3665
- https://bugzilla.redhat.com/show_bug.cgi?id=1147767
- https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-30
- Weakness (CWE)
-- Platform
- Java / Kotlin (Maven)
- Package
org.jenkins-ci.main:jenkins-core- Disclosed
- 17.05.2022
- Updated
- 11.10.2026 12:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-66cr-6whx-732p - 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
-
Jenkins improperly ensures trust separation 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.