VulnerabilityPublished 9 Jul 2025Updated 4 Nov 2025

CVE-2025-53663: Jenkins IBM Cloud DevOps Plugin · CWE-311

Affects Jenkins IBM Cloud DevOps PluginSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 IBM Cloud DevOps Plugin	Affected =0 <=2.0.16	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately audit Jenkins permissions to ensure that only trusted users have Item/Extended Read or higher access, minimizing exposure to sensitive job configurations. 2) Restrict file system access to the Jenkins controller to authorized personnel only, using OS-level access controls and monitoring. 3) Monitor and rotate SonarQube tokens that may have been exposed, invalidating any potentially compromised credentials. 4) Upgrade the Jenkins IBM Cloud DevOps Plugin to a patched version once available from the vendor, or apply any recommended configuration changes that encrypt or protect tokens. 5) Implement secrets management solutions integrated with Jenkins to avoid storing plaintext tokens in config files, such as using Jenkins credentials plugin or external vaults. 6) Regularly review and audit CI/CD pipeline configurations for insecure storage of credentials. 7) Employ network segmentation and monitoring to detect unusual access patterns to Jenkins or SonarQube services. 8) Educate development and DevOps teams about secure handling of authentication tokens and the risks of plaintext storage.

Description

Jenkins IBM Cloud DevOps Plugin 2.0.16 and earlier stores SonarQube authentication tokens unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.

Impact

For European organizations, this vulnerability poses a risk of credential leakage within CI/CD pipelines that use Jenkins integrated with IBM Cloud DevOps and SonarQube. Exposure of SonarQube tokens could allow attackers or unauthorized users to access code quality and security reports, potentially revealing sensitive project information or enabling manipulation of code analysis results. While the vulnerability does not directly compromise Jenkins integrity or availability, the leaked tokens could be used to pivot attacks or gather intelligence on development workflows. Organizations with multi-tenant Jenkins environments or those with less restrictive access controls are at higher risk. This could lead to compliance issues, especially under GDPR, if sensitive project data is exposed. The risk is heightened in environments where Jenkins controllers are accessible to multiple teams or external collaborators. The absence of encryption for stored tokens also indicates a broader security posture concern that may affect other credentials or secrets stored similarly.

CWE-311Missing Encryption of Sensitive Data (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not encrypt sensitive or critical information before storage or transmission.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
Architecture and Design
Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system; Encryption that is needed to protect the system itself from unauthorized disclosure or tampering
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
User Privacy Protection (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V6.1.3 (opens in a new tab)
V6.1.2 (opens in a new tab)
V6.1.1 (opens in a new tab)
Attack patterns
Sniffing Attacks (opens in a new tab)
Sniffing Network Traffic (opens in a new tab)
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Retrieve Embedded Sensitive Data (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:59 UTC

WeaknessesCWE-311

Technical details

References

Community reviews

Related threats