# CVE-2025-26383: Information disclosure in iSTAR Configuration Utility (ICU)

> The iSTAR Configuration Utility leaks memory, potentially exposing unauthorized data from the host Windows PC to attackers.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2025
- **Updated:** 11 Jun 2025
- **Also known as:** GHSA-h6x7-66p5-f6g7

## What is CVE-2025-26383?

CVE-2025-26383 is a medium-severity vulnerability in Johnson Controls iSTAR Configuration Utility (ICU), published on 11 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The iSTAR Configuration Utility (ICU) tool leaks memory, which could result in the unintended exposure of unauthorized data from the Windows PC that ICU is running on.

Weakness: CWE-457 (Use of Uninitialized Variable)

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


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

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

## Is CVE-2025-26383 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26383 is a medium-severity vulnerability in Johnson Controls iSTAR Configuration Utility (ICU), published on 11 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26383 in the wild and no public exploit code.

Affected product: Johnson Controls iSTAR Configuration Utility (ICU). 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-26383/ (Markdown: https://insights.sbomify.com/CVE-2025-26383/index.md)
```

## Sources

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

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