Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Jenkins core (org.jenkins-ci.main:jenkins-core, affected versions from 1.533 before 1.551 and before 1.532.2) does not invalidate a user's API token when that user is deleted. An attacker who already has an authenticated account can keep access to Jenkins using that token after the user has been deleted. Upgrade to Jenkins 1.551 or 1.532.2 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
No source has published a CVSS score for this record yet.
- CISA KEV Not listed.
- EPSS 0.017, the 78th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:12 UTC First seen by agentprime
- 31 Oct 2026, 15:12 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-vxc6-wvh8-fpxw
- OSV: GHSA-vxc6-wvh8-fpxw
- nvd.nist.gov/vuln/detail/CVE-2014-2062
- github.com/jenkinsci/jenkins/commit/5548b5220cfd496831b5721124189ff18fbb12a3
- github.com/jenkinsci/jenkins
- wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-02-14
- www.openwall.com/lists/oss-security/2014/02/21/2