dbcve.org
Devops DeployApplication · Ibm

CVE-2025-14148

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-15
Fix available
A fix is available. Upgrade to 8.1.2.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM UCD - IBM DevOps Deploy 8.1 through 8.1.2.3 could allow an authenticated user with LLM integration configuration privileges to recover a previously saved LLM API Token.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM DevOps Deploy 8.1 through 8.1.2.3 contains a vulnerability where an authenticated user with LLM integration configuration privileges can recover previously saved LLM API tokens, exposing sensitive credentials that should not be retrievable.

MitigationApply the IBM fix pack or update for DevOps Deploy to address this vulnerability. Review and restrict access to LLM integration configuration privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Devops DeployApplication
Affected:>= 8.1.0.0, < 8.1.2.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM DevOps Deploy version
    Locate the IBM DevOps Deploy installation directory and check the version file or use the product's version command. Common locations include the installation root or the about dialog in the web interface.
    Affected if Version is 8.1.0.0 through 8.1.2.3 (less than 8.1.2.4)
  2. Compare version to affected range
    Verify that the installed version falls within the range >= 8.1.0.0 and < 8.1.2.4. Any version from 8.1.0.0 up to and including 8.1.2.3 is affected.
    Affected if Installed version is 8.1.0.0 through 8.1.2.3
  3. Confirm LLM integration is configured
    Check if the LLM integration feature has been configured in the IBM DevOps Deploy environment. This is typically found in the integration or configuration settings of the deployment tool.
    Affected if LLM integration is enabled or has been configured with API tokens
  4. Review user access privileges
    Audit the user roles and permissions within IBM DevOps Deploy, specifically looking for users or groups granted LLM integration configuration privileges.
    Affected if Any authenticated users have LLM integration configuration privileges

User is affected if IBM DevOps Deploy version 8.1.0.0 through 8.1.2.3 is running with LLM integration configured and users possess LLM integration configuration privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.1.2.4 or later
Fixed in 8.1.2.4
Interim mitigation

Apply the IBM fix pack or update for DevOps Deploy to address this vulnerability. Review and restrict access to LLM integration configuration privileges.

Recommended fix High confidence

8.1.2.4

  1. 1. Identify your current IBM DevOps Deploy version by accessing the Administration > System Information page
  2. 2. Create a complete backup of your IBM DevOps Deploy installation including the conf and var directories
  3. 3. Download IBM DevOps Deploy version 8.1.2.4 from the official IBM Fix Central website (https://www.ibm.com/support/fixcentral)
  4. 4. Stop the IBM DevOps Deploy server before applying the update
  5. 5. Apply the version 8.1.2.4 update following IBM's standard upgrade documentation for your deployment type
  6. 6. Restart the IBM DevOps Deploy server
  7. 7. Verify the upgrade was successful by checking the version in Administration > System Information
  8. 8. Log in and confirm that LLM integration configuration works properly with the fixed version
Caveat Review IBM's release notes for 8.1.2.4 for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devops Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14148 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14148 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data