CVE-2026-56460
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 · uneditedHCL DevOps Deploy / HCL Launch 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 · moderate confidenceHCL DevOps Deploy and HCL Launch contain an information disclosure vulnerability where authenticated users can receive sensitive configurations and secrets (such as passwords, API keys, or credentials) within API responses. This allows any authenticated user to potentially access credential material they should not have access to, which could then be leveraged for further attacks against the system or connected resources.
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.2.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 HCL product and versionLocate the installed version of HCL DevOps Deploy or HCL Launch. This is typically found in the product's about page, version file, or by querying the product's built-in version endpoint. Common locations include the installation directory's version metadata or the /rest/version API endpoint.Affected if The installed version falls within any of these ranges: HCL DevOps Deploy 8.0.0.0 to 8.0.1.13, 8.1.0.0 to 8.1.2.6, or 8.2.0.0 to 8.2.1.x; HCL Launch 7.3.0.0 to 7.3.2.18.
-
Confirm product typeDetermine whether the installation is HCL DevOps Deploy (formerly UrbanCode Deploy) or HCL Launch (formerly UrbanCode Release). Both products share this vulnerability but have different version numbering.Affected if The product is either HCL DevOps Deploy or HCL Launch and the version matches the affected ranges.
-
Verify API access is enabledConfirm that the product's API interface is accessible. This includes REST API endpoints typically available on ports 8080 or 8443. Check if the web application is running and accepting requests.Affected if The API interface is accessible and the product version is within the affected ranges.
-
Check for sensitive data in API responsesIf safe to do so in a non-production environment, make an authenticated API call to common endpoints (such as resource or configuration endpoints) and inspect whether passwords, API keys, or credentials appear in plain text in the JSON response. Alternatively, review API endpoint documentation or test results that show sample output.Affected if The product is a vulnerable version AND API endpoints return unmasked sensitive configuration data to authenticated users.
You are affected if your installed HCL DevOps Deploy version is 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.1.x; or your HCL Launch version is 7.3.0.0 through 7.3.2.18, and the product's API is accessible to authenticated users.
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
Review and modify all API endpoints to ensure sensitive configuration data, credentials, and secrets are filtered, redacted, or masked in responses returned to users, regardless of their authentication status. Implement proper data classification and output encoding for API responses.
HCL DevOps Deploy: 8.0.1.14, 8.1.2.7, or 8.2.2.0 (depending on your current major.minor); HCL Launch: 7.3.2.19
- Identify the exact version of HCL DevOps Deploy or HCL Launch currently installed
- For HCL DevOps Deploy 8.0.x: Upgrade to version 8.0.1.14 or later
- For HCL DevOps Deploy 8.1.x: Upgrade to version 8.1.2.7 or later
- For HCL DevOps Deploy 8.2.x: Upgrade to version 8.2.2.0 or later
- For HCL Launch 7.3.x: Upgrade to version 7.3.2.19 or later
- After upgrade, verify the fix by testing API responses to confirm sensitive data is no longer exposed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56460 — 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-56460 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