NplatformApplication · Nuvationenergy

CVE-2025-64121

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-02
Fix available
A fix is available. Upgrade to 2.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authentication Bypass Using an Alternate Path or Channel vulnerability in Nuvation Energy Multi-Stack Controller (MSC) allows Authentication Bypass.This issue affects Multi-Stack Controller (MSC): from 2.3.8 before 2.5.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Critical authentication bypass vulnerability in Nuvation Energy Multi-Stack Controller (MSC) allows unauthenticated attackers to circumvent authentication mechanisms. The vulnerability affects versions 2.3.8 through versions prior to 2.5.1, enabling complete compromise of the controller which manages energy storage systems.

MitigationUpgrade Multi-Stack Controller firmware to version 2.5.1 or later to remediate the authentication bypass vulnerability. If immediate patching is not feasible, implement network segmentation and restrict access to the MSC management interfaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NplatformApplication
Affected:>= 2.3.8, < 2.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nuvation Energy MSC installation
    Check system documentation, software inventory, or network scan for Nuvation Energy Multi-Stack Controller or Nplatform. Look for service banners, open ports associated with MSC (typically ports 80/443 for web interfaces), or check with: `grep -i 'nuvation' /etc/services` or review asset inventory.
    Affected if The system runs Nuvation Energy Multi-Stack Controller (MSC) or Nplatform software.
  2. Determine installed firmware version
    Access the MSC web interface or check via administrative CLI/console. Look for version information in the About page, system status, or firmware metadata. If using command-line: `show system info` or `cat /version` depending on available interface.
    Affected if Installed version is >= 2.3.8 and < 2.5.1.
  3. Verify MSC management interface exposure
    Check network configuration to determine if MSC web interface (typically HTTP/HTTPS on ports 80/443 or custom ports) is accessible from untrusted networks. Use `netstat -tlnp` or `nmap -p 80,443 <target>` to identify exposed management ports.
    Affected if MSC management interface is reachable from network segments that are not isolated or are accessible to untrusted users.
  4. Confirm authentication mechanism is in use
    Test whether the MSC login page is accessible and authentication is enforced. Attempt to access protected endpoints without credentials. Check if the bypass allows access to administrative functions without valid credentials.
    Affected if Authentication can be bypassed and administrative functions are accessible without credentials.

User is affected if Nuvation Energy Nplatform/MSC firmware version is 2.3.8 or higher but below 2.5.1 AND the MSC management interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.5.1 or later
Fixed in 2.5.1
Interim mitigation

Upgrade Multi-Stack Controller firmware to version 2.5.1 or later to remediate the authentication bypass vulnerability. If immediate patching is not feasible, implement network segmentation and restrict access to the MSC management interfaces.

Recommended fix High confidence

Nplatform 2.5.1

  1. Identify all Nuvation Energy Multi-Stack Controller (MSC) devices running Nplatform versions 2.3.8 through 2.5.0 in the environment
  2. Confirm the current Nplatform version on each affected device
  3. Obtain the Nplatform 2.5.1 release from Nuvation Energy or authorized distribution channels
  4. Follow vendor-provided upgrade procedures to update each affected MSC device from its current version to version 2.5.1
  5. After upgrade, verify the Nplatform version reads 2.5.1 or higher
  6. Confirm the authentication bypass vulnerability is no longer present by testing the authentication mechanism

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nplatform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64121 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data