VulnerabilityPublished 9 Jul 2025Updated 4 Nov 2025

CVE-2025-53655: Jenkins Statistics Gatherer Plugin · CWE-256

Affects Jenkins Statistics Gatherer PluginSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Jenkins Project Jenkins Statistics Gatherer Plugin	Affected =0 <=2.0.3	Fixed in–

AI-suggested

Immediately restrict access to the Jenkins global configuration interface to trusted administrators only, using network segmentation and strong authentication mechanisms such as multi-factor authentication (MFA).
Monitor Jenkins access logs for any unauthorized or suspicious access attempts to the configuration pages.
Until an official patch is released, consider removing or disabling the Statistics Gatherer Plugin if it is not essential to your CI/CD pipeline.
Rotate AWS Secret Keys that have been configured in Jenkins to invalidate any potentially exposed credentials.
Implement AWS IAM policies with least privilege principles to limit the impact of any leaked credentials.
Use Jenkins credentials management features or secret management tools that properly mask and encrypt sensitive information instead of storing secrets in plugin configuration forms.
Stay informed about updates from the Jenkins project and apply patches promptly once available.
Conduct regular security audits of Jenkins plugins and configurations to detect similar issues proactively.

Description

Jenkins Statistics Gatherer Plugin 2.0.3 and earlier does not mask the AWS Secret Key on the global configuration form, increasing the potential for attackers to observe and capture it.

Impact

For European organizations, the impact of this vulnerability is primarily the risk of AWS credential leakage, which can lead to unauthorized access to cloud resources. This could result in data breaches, unauthorized modification or deletion of cloud assets, increased cloud costs due to resource misuse, and potential compliance violations under regulations like GDPR if personal data is involved. Organizations relying heavily on AWS for critical infrastructure or sensitive data processing are at greater risk. The vulnerability's ease of exploitation without authentication means that any attacker who gains access to Jenkins UI or configuration files can capture the AWS Secret Key. This elevates the threat level in environments where Jenkins access controls are weak or compromised. Additionally, the exposure could facilitate lateral movement within an organization's cloud environment, amplifying the potential damage. The medium severity rating reflects the limited scope of impact to confidentiality, but the critical nature of AWS credentials means the actual operational risk can be substantial if exploited. European entities with cloud-heavy DevOps practices must prioritize addressing this vulnerability to prevent potential cloud security incidents.

CWE-256Plaintext Storage of a Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores a password in plaintext within resources such as memory or files.
Architecture and Design
Avoid storing passwords in easily accessible locations.
Architecture and Design
Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
A programmer might attempt to remedy the password management problem by obscuring the password with an encoding function, such as base 64 encoding, but this effort does not adequately protect the password because the encoding can be detected and decoded easily.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.7.5 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 21:57 UTC

WeaknessesCWE-256

Technical details

References

Community reviews

Related threats