Advisory record · GHSA-vxc6-wvh8-fpxw

Jenkins does not invalidate the API token when a user is deleted

No CVSS scoreEPSS 0.017 · 78th percentile

Published by the GitHub Advisory Database at 17 May 2022, 03:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.jenkins-ci.main:jenkins-coreMaven>=1.533, <1.551 || <1.532.21.551, 1.532.2
Identifiers
GHSA-vxc6-wvh8-fpxw · CVE-2014-2062
Weakness (CWE)
CWE-287
Published
17 May 2022
Updated
3 Dec 2024

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.

Written 8 Nov 2026.

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

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.