CVE-2026-56458
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 uses Cross-Origin Resource Sharing (CORS) which could allow an attacker to carry out privileged actions and retrieve sensitive information as the domain name is not being limited to only trusted domains.
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 has a CORS misconfiguration where the application does not properly validate the Origin header against an allowlist of trusted domains. This allows any malicious website to make cross-origin requests on behalf of authenticated users, potentially enabling privileged actions and exfiltration of sensitive data.
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.1.0.0, < 8.1.2.7>= 8.2.0.0, < 8.2.2.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 HCL DevOps Deploy versionCheck the product version through the admin console UI (typically at /ibm/console or /deployit), or check version files in the installation directory such as version.txt or about.properties in the installation rootAffected if Version is >= 8.1.0.0 and < 8.1.2.7, OR >= 8.2.0.0 and < 8.2.2.0
-
Locate CORS configurationSearch for CORS-related settings in the server configuration files - typically in server.xml, web.xml, or dedicated cors.xml files within the installation conf directory, or check for custom CORS filter configurationsAffected if CORS configuration exists and allows cross-origin requests from any domain
-
Inspect Access-Control-Allow-Origin header handlingExamine the CORS configuration to determine how the Access-Control-Allow-Origin header is set - look for whether it uses an explicit allowlist or reflects the Origin header value from incoming requestsAffected if The configuration reflects the Origin header value back to the client (e.g., uses 'Origin' from request instead of a fixed allowlist) or does not validate against an allowlist
-
Verify Origin header validationSend a test request with a malicious Origin header (e.g., Origin: http://malicious-site.com) and inspect the response headers to see if the server returns Access-Control-Allow-Origin with that arbitrary originAffected if The server returns the arbitrary Origin in the Access-Control-Allow-Origin header without validation
You are affected if your installed version falls within the affected ranges AND the CORS configuration does not validate the Origin header against a trusted allowlist, instead reflecting arbitrary Origins back to clients.
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 · scoped8.1.2.78.2.2.0
Configure CORS to explicitly validate and restrict the Access-Control-Allow-Origin header to only trusted domains, using an explicit allowlist rather than reflecting arbitrary Origins back to the client.
8.1.2.7 for 8.1.x users; 8.2.2.0 for 8.2.x users
- Identify your current version of HCL DevOps Deploy by checking the product UI or installation directory
- If running version 8.1.0.0 through 8.1.2.6, upgrade to version 8.1.2.7 or later
- If running version 8.2.0.0 through 8.2.1.x, upgrade to version 8.2.2.0 or later
- Download the appropriate fix from support.hcl-software.com
- Backup your current installation and configuration before upgrading
- Install the upgraded version following HCL's standard installation procedures
- Verify the CORS configuration is now restricted to trusted domains only
- Test that legitimate cross-origin requests from trusted domains still function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56458 — 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-56458 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