# CVE-2025-52611: HCL iControl was affected by Unhandled Exception - Stack Trace Disclosure vulnerability

> An attacker can trigger an unhandled exception in HCL iControl to disclose stack traces, potentially revealing internal application details.

- **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:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-v6rp-8fmq-j68m

## What is CVE-2025-52611?

CVE-2025-52611 is a low-severity vulnerability in HCL iControl, published on 4 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HCL iControl v4.0.0 was affected by Unhandled Exception - Stack Trace Disclosure vulnerability. The error occurs due to an undefined property being accessed in the application's JavaScript code. Specifically, the code attempts to read the property dashboard key from an object that is undefined. This issue likely stems from one of the following: A missing or improperly initialized object.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2025-52611?

It affects 1 product.


Products: Hcltech Icontrol.

## How do I fix CVE-2025-52611?

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

## Is CVE-2025-52611 being exploited?

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

## Other vulnerabilities in HCL iControl

- [CVE-2025-52612](https://insights.sbomify.com/CVE-2025-52612/): HCL iControl was affected by Export CSV - CSV Injection vulnerability. (high 7.1)
- [CVE-2026-56567](https://insights.sbomify.com/CVE-2026-56567/): HCL iControl is affected by multiple security vulnerabilities. (medium 5.1)
- [CVE-2026-56609](https://insights.sbomify.com/CVE-2026-56609/): HCL iControl is affected by multiple security vulnerabilities(CVE-2026-56608 and CVE-2026-56609). (medium 4.8)
- [CVE-2025-52606](https://insights.sbomify.com/CVE-2025-52606/): HCL iControl was affected by Weak Input Validation vulnerability. . (medium 4.3)
- [CVE-2026-56569](https://insights.sbomify.com/CVE-2026-56569/): HCL iControl is affected by multiple security vulnerabilities. (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52611 and fix it if it is affected.

What it is: CVE-2025-52611 is a low-severity vulnerability in HCL iControl, published on 4 Jun 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-2025-52611 in the wild and no public exploit code.

Affected product: HCL iControl. 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-2025-52611/ (Markdown: https://insights.sbomify.com/CVE-2025-52611/index.md)
```

## Sources

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

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