CVE-2025-14148VulnerabilityPublished 15 Dec 2025

CVE-2025-14148: UCD – IBM DevOps Deploy · Insufficiently Protected Credentials

Affects UCD – IBM DevOps DeploySource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% 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 15 Dec 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 2026-10-26.

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 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
IBM UCD - IBM DevOps Deploy	Affected =8.1	Fixed in–

AI-suggested

To mitigate CVE-2025-14148, organizations should first apply any patches or updates provided by IBM once available. In the absence of immediate patches, restrict LLM integration configuration privileges strictly to trusted administrators and implement role-based access controls to minimize the number of users with such privileges. Conduct regular audits of configuration changes and access logs to detect unauthorized attempts to retrieve API tokens. Consider encrypting stored tokens using strong cryptographic methods beyond the default product storage mechanisms, if feasible. Implement token rotation policies to limit the lifespan of exposed tokens and reduce potential misuse. Additionally, monitor LLM API usage for anomalous activity that could indicate token compromise. Educate DevOps teams on the risks of credential exposure and enforce the principle of least privilege in all automation tools. Finally, segregate environments and sensitive integrations to contain potential breaches.

Description

CVE-2025-14148 is a medium severity vulnerability in IBM UCD - IBM DevOps Deploy versions 8.1 through 8.1.2.3. It allows an authenticated user with LLM integration configuration privileges to recover a previously saved LLM API token due to insufficient credential protection (CWE-522). The vulnerability does not require user interaction and can be exploited remotely with low attack complexity. While it impacts confidentiality by exposing sensitive API tokens, it does not affect integrity or availability. No known exploits are currently in the wild. European organizations using IBM DevOps Deploy for automation and integration with LLM services should prioritize patching or mitigating this issue to prevent unauthorized access to API tokens.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive API tokens used in DevOps automation workflows. Exposure of LLM API tokens could allow attackers to misuse LLM services, potentially leading to unauthorized data access, injection of malicious commands, or manipulation of automated deployment processes. Organizations relying on IBM UCD for critical software delivery pipelines may face increased insider threat risks or compromise from attackers who gain configuration privileges. The impact is particularly relevant for sectors with stringent data protection requirements such as finance, healthcare, and government, where unauthorized access to integrated AI services could lead to compliance violations or data breaches. While the vulnerability does not directly affect system integrity or availability, the indirect consequences of token misuse could disrupt operations or expose sensitive intellectual property. Given the widespread use of IBM DevOps Deploy in large enterprises across Europe, the vulnerability could affect a broad range of organizations, especially those integrating LLM capabilities into their CI/CD pipelines.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7254663 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Dec 2025, 20:39 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats