# CVE-2025-61738: Johnson Controls PowerG and IQPanel cleartext transmission of sensitive information

> Attackers can capture network keys and read or write encrypted packets on the PowerG network, compromising security panel communications.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-8953-5927-ff93

## What is CVE-2025-61738?

CVE-2025-61738 is a low-severity vulnerability in Johnson Controls IQPanel2,	IQHub,IQPanel2+,IQPanel 4,PowerG, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Under certain circumstances, attacker can capture the network key, read or write encrypted packets on the PowerG network.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-61738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61738 is a low-severity vulnerability in Johnson Controls IQPanel2,	IQHub,IQPanel2+,IQPanel 4,PowerG, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-61738 in the wild and no public exploit code.

Affected product: Johnson Controls IQPanel2,	IQHub,IQPanel2+,IQPanel 4,PowerG. 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-61738/ (Markdown: https://insights.sbomify.com/CVE-2025-61738/index.md)
```

## Sources

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

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