# CVE-2025-9696: Use of Hard-coded Credentials in SunPower PVS6

> Attackers within Bluetooth range can use hardcoded credentials to gain full control of the SunPower PVS6 solar inverter, enabling firmware replacement and grid manipulation.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 2 Sep 2025
- **Updated:** 2 Sep 2025

## What is CVE-2025-9696?

CVE-2025-9696 is a critical vulnerability in SunPower PVS6, published on 2 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SunPower PVS6's BluetoothLE interface is vulnerable due to its use of hardcoded encryption parameters and publicly accessible protocol details. An attacker within Bluetooth range could exploit this vulnerability to gain full access to the device's servicing interface. This access allows the attacker to perform actions such as firmware replacement, disabling power production, modifying grid settings, creating SSH tunnels, altering firewall settings, and manipulating connected devices.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-9696 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9696 is a critical vulnerability in SunPower PVS6, published on 2 Sep 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-9696 in the wild and no public exploit code.

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

## Sources

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

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