Device takeover via shared Bluetooth encryption key
Published Sep 2, 2025 · Updated Sep 2, 2025
Hardcoded credentials in SunPower PVS6 2025.06 build 61839 and earlier allow physically proximate attackers to control it via Bluetooth. The Bluetooth LE protocol encrypts servicing requests with AES-128-CBC using one preshared key across devices and an all-zero initialization vector. Bluetooth range plus knowledge of the protocol and shared key permits reading system data, changing network and grid settings, disabling power production, and initiating signed firmware updates.
Summary
What happened
Hardcoded credentials in SunPower PVS6 2025.06 build 61839 and earlier allow physically proximate attackers to control it via Bluetooth. The Bluetooth LE protocol encrypts servicing requests with AES-128-CBC using one preshared key across devices and an all-zero initialization vector. Bluetooth range plus knowledge of the protocol and shared key permits reading system data, changing network and grid settings, disabling power production, and initiating signed firmware updates.
The record
- CVE
- CVE-2025-9696
- Published
- Sep 2, 2025
- Updated
- Sep 2, 2025
- Vendor
- SunPower
- Product
- PVS6
- Classifications
- CWE-798, T0866
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2025.06 build 61839
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo