# CVE-2026-21764: Insufficient Input Validation in DevOps Loop

> Insufficient input validation in HCL DevOps Loop allows special characters, potentially causing unintended application behavior.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/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 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-35w6-wm82-6c6f

## What is CVE-2026-21764?

CVE-2026-21764 is a low-severity vulnerability in HCLSoftware DevOps Loop, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL DevOps Loop is affected by insufficient input validation that allows special characters where they should be restricted. This may result in unintended application behavior under certain conditions.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 1 product.


Products: Hcltech Devops Loop.

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

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

## Is CVE-2026-21764 being exploited?

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

## Other vulnerabilities in HCLSoftware DevOps Loop

- [CVE-2026-21760](https://insights.sbomify.com/CVE-2026-21760/): Unauthorized Access to Admin Functionality via Forced Browsing (medium 4.6)
- [CVE-2026-21761](https://insights.sbomify.com/CVE-2026-21761/): CORS Misconfiguration in DevOps Loop (medium 4.2)
- [CVE-2026-21762](https://insights.sbomify.com/CVE-2026-21762/): Missing HTTP Security Headers in DevOps Loop (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21764 is a low-severity vulnerability in HCLSoftware DevOps Loop, published on 17 Jul 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-21764 in the wild and no public exploit code.

Affected product: HCLSoftware DevOps Loop. 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-21764/ (Markdown: https://insights.sbomify.com/CVE-2026-21764/index.md)
```

## Sources

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

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