# CVE-2026-67071: Information disclosure in HCL DevOps Deploy / HCL Launch

> Attackers can view sensitive secure property values due to redaction failures when specific non-ASCII characters are used in deployment configurations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-qw5g-vf8h-crwx

## What is CVE-2026-67071?

CVE-2026-67071 is a medium-severity vulnerability in HCLSoftware HCL DevOps Deploy / HCL Launch, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL DevOps Deploy / HCL Launch is susceptible to an information disclosure vulnerability when processing redacted property values. If a deployment is configured with a secure property that starts with certain non-ASCII characters, the redaction engine may fail to mask subsequent ASCII secure values embedded inside insecure properties.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

## Which versions are affected by CVE-2026-67071?


## How do I fix CVE-2026-67071?

No fix has been published for CVE-2026-67071 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-67071 being exploited?

There is no known exploitation of CVE-2026-67071 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67071 and fix it if it is affected.

What it is: CVE-2026-67071 is a medium-severity vulnerability in HCLSoftware HCL DevOps Deploy / HCL Launch, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-67071 in the wild and no public exploit code.

Affected product: HCLSoftware HCL DevOps Deploy / HCL Launch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67071/ (Markdown: https://insights.sbomify.com/CVE-2026-67071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67071
- OSV: https://osv.dev/vulnerability/CVE-2026-67071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67071/
Summaries are generated and may contain mistakes; the official description above is the record.