CVE-2026-12085
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 · uneditedIBM 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 responses that could be used in further attacks against the system.
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 · high confidenceIBM UrbanCode Deploy and DevOps Deploy contain an information disclosure vulnerability where authenticated users can receive sensitive configurations and secrets in API responses that should not be accessible to them. The API improperly exposes sensitive data that could be leveraged for further attacks against the system.
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>= 8.0.0.0, < 8.0.1.14>= 8.1.0.0, < 8.1.2.7>= 8.2.0.0, < 8.2.1.0>= 7.3.0.0, < 7.3.2.19CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of IBM UrbanCode Deploy or DevOps DeployAccess the product's admin console or check the version information through the product's about/settings page. Alternatively, look for version details in the product's installation directory or startup logs.Affected if The installed version falls within any of these ranges: DevOps Deploy 8.0.0.0 through 8.0.1.13, 8.1.0.0 through 8.1.2.6, or 8.2.0.0 through 8.2.0.x; UrbanCode Deploy 7.3.0.0 through 7.3.2.18.
-
Confirm the API is accessible to authenticated usersVerify that the product's REST API endpoints are enabled and accessible. Typically this involves checking that the web application is running and that user authentication is configured.Affected if The API is available to standard authenticated users without elevated privileges.
-
Audit API responses for unintended sensitive data exposureAs an authenticated user with standard permissions, make API calls to common endpoints (such as resource, component, or process endpoints) and inspect the JSON responses. Look for fields that may contain passwords, tokens, configuration secrets, or other credentials that should not be visible to that user role.Affected if API responses contain sensitive fields such as passwords, secure properties, API tokens, or configuration secrets that the authenticated user should not have access to based on their role.
-
Review API endpoint access control configurationsExamine the product's role-based access control (RBAC) settings for API resources. Check whether proper filtering is applied to prevent users from retrieving resources or configurations they are not authorized to view.Affected if API endpoints return data for resources or configurations that the requesting user does not have explicit permission to access.
A user is affected if their installed product version is within the affected ranges AND the product's API is accessible to authenticated users who can receive sensitive data in responses they should not be authorized to see.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.3.2.198.0.1.148.1.2.7
Apply vendor patches for the affected versions (7.3.2.19+, 8.0.1.14+, 8.1.2.7+, 8.2.1.1+) and conduct a thorough audit of API response data to identify and remediate any other instances of sensitive information leakage.
IBM DevOps Deploy 8.0.1.14+ (8.0.x), 8.1.2.7+ (8.1.x), 8.2.1.0+ (8.2.x) or IBM UrbanCode Deploy 7.3.2.19+
- Identify your current IBM UrbanCode Deploy or DevOps Deploy version from the product UI or release notes
- Download the appropriate fixed version from IBM Fix Central or the IBM Passport Advantage site: For DevOps Deploy 8.0.x, upgrade to 8.0.1.14 or later; For DevOps Deploy 8.1.x, upgrade to 8.1.2.7 or later; For DevOps Deploy 8.2.x, upgrade to 8.2.1.0 or later; For UrbanCode Deploy 7.3.x, upgrade to 7.3.2.19 or later
- Review the IBM installation documentation for your version to understand the upgrade process
- Create a complete backup of your current installation including the conf, var, and install directories
- Stop the IBM UrbanCode Deploy or DevOps Deploy server and agent services
- Run the IBM installation manager or appropriate upgrade installer for your chosen fixed version
- After installation, verify the server starts successfully and check the logs for any errors
- Test that API responses no longer contain sensitive configuration data or secrets in the areas previously affected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12085 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12085 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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