Advisory record · GHSA-8pqx-3rxx-f5pm

Jenkins discloses project names via fingerprints

CVSS 7.5 HighCriticalIn CISA KEVEPSS 0.23 · 97th percentile

Critical, because:

  • In CISA’s KEV catalogue since 12 May 2023: it is known to be exploited.
  • CVSS score 7.5 (7.0 or more) and EPSS 0.23 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 13 May 2022, 01:30 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.625.2 || >=1.626, <1.6381.625.2, 1.638
Identifiers
GHSA-8pqx-3rxx-f5pm · CVE-2015-5317
Weakness (CWE)
CWE-200
Published
13 May 2022
Updated
22 Oct 2025

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) versions below 1.625.2, and versions from 1.626 up to but not including 1.638, are affected. The Fingerprints pages may let a remote attacker obtain sensitive job and build names through a direct request. Upgrade to 1.625.2 or 1.638, or later. The source gives few details about the exact conditions required for the attack.

Written 7 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

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:H GitHub Advisory Database
  • CISA KEV Listed since 12 May 2023: known to be exploited.
  • EPSS 0.23, the 97th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 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.