dbcve.org
CWE-441Weakness · CWE-441

CVE-2025-64125

CRITICAL · 9.4 CVSS v4.0 Published 2026-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
98/100
Remediation priority · Urgent
Remotely reachable

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
A vulnerability in Nuvation Energy nCloud VPN Service allowed Network Boundary Bridging.This issue affected the nCloud VPN Service and was fixed on 2025-12-1 (December, 2025). End users do not have to take any action to mitigate the issue.

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 · low confidence

A vulnerability in Nuvation Energy nCloud VPN Service allowed network boundary bridging, potentially enabling unauthorized communication between normally isolated network segments.

MitigationThe vulnerability was patched on 2025-12-1; organizations should verify they are running the updated nCloud VPN Service version.

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

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
Low
Authentication
X
User interaction
P
Scope
P

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:X/R:X/V:X/RE:X/U:X

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 if nCloud VPN Service is installed
    On the system running the VPN service, check for the presence of nCloud VPN Service processes or installed software. Look for processes named 'ncloud', 'nCloud VPN', or related service executables. On Windows, check Services list; on Linux, check running services or systemctl list-units.
    Affected if The nCloud VPN Service executable or service is found running on the system.
  2. Determine the installed nCloud VPN Service version
    Query the installed version of nCloud VPN Service. This may be available via: (1) Software inventory or installed programs list, (2) The service executable properties (right-click > Properties > Details), (3) A command-line flag like 'ncloud -v' or 'ncloud --version' if available, (4) Registry keys on Windows (HKLM\Software\NuvationEnergy\nCloud) or config files on Linux.
    Affected if The installed version is older than the patched version released on 2025-12-1, or the version cannot be determined (unknown).
  3. Review VPN network configuration for boundary bridging
    Examine the nCloud VPN Service configuration files and network settings to determine if the VPN is configured to bridge or route between different network segments. Look for settings related to 'bridge', 'routing', 'network segments', 'subnets', or 'interface bonding'. Check if multiple distinct network ranges are being allowed to communicate through the VPN tunnel.
    Affected if The VPN configuration explicitly enables bridging between isolated network segments or allows routing between normally separated network boundaries.
  4. Check VPN service exposure and access controls
    Review the network exposure of the nCloud VPN Service. Determine: (1) Is the VPN service listening on external/accessible network interfaces? (2) Are there authentication requirements enforced? (3) Check firewall rules or access control lists governing who can connect to the VPN. Look for configuration files in the nCloud installation directory for listen addresses and access policies.
    Affected if The VPN service is exposed to untrusted networks without proper network segmentation controls or authentication enforcement.

A defender is affected if the nCloud VPN Service is installed and running with a version released before 2025-12-1, or if the VPN configuration allows bridging between isolated network segments to untrusted interfaces.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The vulnerability was patched on 2025-12-1; organizations should verify they are running the updated nCloud VPN Service version.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-64125 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