# CVE-2026-21836: HCL DominoIQ is affected by broken access control

> An authenticated attacker can bypass document-level access restrictions in the RAG feature to view sensitive data.

- **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:** 20 May 2026
- **Updated:** 21 May 2026
- **Also known as:** GHSA-2qq9-gw9m-g2rg

## What is CVE-2026-21836?

CVE-2026-21836 is a medium-severity missing authorization vulnerability in HCLSoftware DominoIQ, published on 20 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The HCL DominoIQ RAG feature is affected by a Broken Access Control vulnerability.  Under certain circumstances, document level access restrictions will be ignored when determining what data to return from an AI query.  This could enable an authenticated attacker to view sensitive data.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-21836 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21836 is a medium-severity missing authorization vulnerability in HCLSoftware DominoIQ, published on 20 May 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-21836 in the wild and no public exploit code.

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

## Sources

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

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