Cyber Resilience

CVE-2026-12085

Info Disclosure in Ibm Devops Deploy 8.0.0.0 – 8.0.1.14

Published
30 June 2026
Modified
02 July 2026
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-12085 is a medium-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Ibm Devops Deploy. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM UCD - IBM UrbanCode Deploy 7.3 through 7.3.2.18 and IBM UCD - IBM DevOps Deploy 8.0 through 8.0.1.13, 8.1 through 8.1.2.6, and 8.2 through 8.2.1.0 IBM DevOps Deploy could disclose sensitive configurations and secrets to authenticated users in API…

more

responses that could be used in further attacks against the system.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Why these techniques?

Direct exposure of secrets/configs via API enables unsecured credential access (T1552).

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-28781Same product: Ibm Devops Deploy
CVE-2024-22358Same product: Ibm Devops Deploy
CVE-2024-54176Same product: Ibm Devops Deploy
CVE-2025-1998Same product: Ibm Devops Deploy
CVE-2024-51472Same product: Ibm Devops Deploy
CVE-2024-22331Same product: Ibm Devops Deploy
CVE-2025-36360Same product: Ibm Devops Deploy
CVE-2024-22334Same product: Ibm Devops Deploy
CVE-2026-12086Same product: Ibm Devops Deploy
CVE-2025-1997Same product: Ibm Devops Deploy

Affected Assets

ibm
devops deploy
8.0.0.0 — 8.0.1.14 · 8.1.0.0 — 8.1.2.7 · 8.2.0.0 — 8.2.1.0
ibm
urbancode deploy
7.3.0.0 — 7.3.2.19

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-4 Information Flow Enforcement
  • AC-3 Access Enforcement
  • SI-15 Information Output Filtering
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Enforces information flow policies to block unauthorized disclosure of sensitive configurations and secrets in API responses.

prevent

Enforces access control policies so that authenticated users cannot retrieve secrets and configurations they are not authorized to view.

prevent

Filters sensitive information from system outputs (API responses) before it is returned to users.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
prevents

Protecting data-in-use includes removing confidential values before they are processed or sent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

mitigates

Information-transfer rules directly govern what data may be sent to external parties.

mitigates

PII-protection requirements reduce the chance of sending personal data to unauthorized recipients.

mitigates

DLP controls inspect and block outbound flows that contain sensitive information.

References