dbcve.org
Memory LeakWeakness · CWE-401

CVE-2025-14027

HIGH · 8.7 CVSS v4.0 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
Multiple denial-of-service vulnerabilities exist in the affected product. These issues can be triggered through various crafted inputs, including malformed Class 3 messages, memory leak conditions, and other resource exhaustion scenarios. Exploitation may cause the device to become unresponsive and, in some cases, result in a major nonrecoverable fault. Recovery may require a restart.

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

This is a HIGH-severity denial-of-service vulnerability involving multiple attack vectors: malformed Class 3 protocol messages (likely DNP3), memory leak conditions, and other resource exhaustion scenarios. Successful exploitation can cause the device to become unresponsive and potentially enter a nonrecoverable fault state requiring physical restart.

MitigationImplement robust input validation for all incoming protocol messages, fix memory management to prevent leaks, and add resource limits/timeouts to prevent exhaustion. Network segmentation and firewall rules can help block malformed traffic.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/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:X/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 DNP3 protocol usage in the environment
    Inventory all systems and devices running DNP3 (Distributed Network Protocol 3) services. Check network scans for port 20000/TCP (typical DNP3) or custom ports configured for DNP3 communication.
    Affected if DNP3 protocol is actively running or enabled on any system in the environment
  2. Determine if Class 3 messages are processed
    Review DNP3 master/outstation configuration to confirm whether Class 3 (critical/urgent) point data requests and responses are enabled. Check protocol analyzer logs for Class 3 message types (often identified by IIN bits or application layer fragments).
    Affected if Class 3 message processing is enabled in the DNP3 implementation
  3. Assess network exposure of DNP3 services
    Verify whether DNP3 ports are accessible from untrusted networks or the internet. Check firewall rules, ACLs, and network segmentation for DNP3 traffic sources.
    Affected if DNP3 services are reachable from networks outside the trusted operational technology zone
  4. Monitor for memory leaks or resource exhaustion
    Observe system memory usage, CPU load, and network connection counts on DNP3-enabled devices over time. Check for abnormal growth patterns or depletion that coincides with protocol activity.
    Affected if Device exhibits progressive memory increase or resource depletion during normal DNP3 operation
  5. Check for device availability and restart requirements
    Review system logs, heartbeat monitors, and incident reports for unexpected device unresponsiveness, crashes, or unexpected shutdowns requiring physical intervention.
    Affected if Devices have experienced unexplained DoS events or required physical restart

The environment is affected if DNP3 protocol is in use, Class 3 message processing is enabled, and the DNP3 interface is accessible to potentially malicious Class 3 protocol messages.

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

Implement robust input validation for all incoming protocol messages, fix memory management to prevent leaks, and add resource limits/timeouts to prevent exhaustion. Network segmentation and firewall rules can help block malformed traffic.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14027 — 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-14027 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