# CVE-2026-66247: Other in iControl

> Insecure CORS policy in HCL iControl allows attackers to exfiltrate sensitive data from victim sessions via malicious cross-origin requests.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/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:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-6wc6-h2p5-23f3

## What is CVE-2026-66247?

CVE-2026-66247 is a medium-severity vulnerability in HCL Software iControl, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

iControl is affected by an insecure Cross-Origin Resource Sharing (CORS) policy vulnerability, which could allow a malicious website to execute cross-origin requests with included credentials, enabling an attacker to access and exfiltrate sensitive data within the context of the victim's active session.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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


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

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

## Is CVE-2026-66247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66247 is a medium-severity vulnerability in HCL Software iControl, published on 1 Oct 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-66247 in the wild and no public exploit code.

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

## Sources

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

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