Nuvation Energy Battery Management System up to 2.3.9 client-side authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Nuvation Energy Battery Management System up to 2.3.9. It has been classified as very critical. Affected by this vulnerability is an unknown functionality. The manipulation leads to use of client-side authentication. This vulnerability is traded as CVE-2025-64119. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Nuvation Energy Battery Management System up to 2.3.9 and classified as very critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a use of client-side authentication vulnerability. Using CWE to declare the problem leads to CWE-603. A client/server product performs authentication within client code but not in server code, allowing server-side authentication to be bypassed via a modified client that omits the authentication check. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A vulnerability in Nuvation Battery Management System allows Authentication Bypass.This issue affects Battery Management System: through 2.3.9.
The weakness was shared by Reid Wightman. The advisory is shared at dragos.com. The identification of this vulnerability is CVE-2025-64119 since 10/27/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/04/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-206227). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use of client-side authenticationCWE: CWE-603 / CWE-602
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/27/2025 CVE reserved01/02/2026 Advisory disclosed
01/02/2026 VulDB entry created
01/04/2026 VulDB entry last update
Sources
Advisory: dragos.comResearcher: Reid Wightman
Status: Not defined
CVE: CVE-2025-64119 (🔒)
GCVE (CVE): GCVE-0-2025-64119
GCVE (VulDB): GCVE-100-339449
EUVD: 🔒
Entry
Created: 01/02/2026 23:18Updated: 01/04/2026 01:56
Changes: 01/02/2026 23:18 (66), 01/03/2026 08:01 (1), 01/04/2026 01:56 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.