dbcve.org
Double FreeWeakness · CWE-415

CVE-2026-12659

HIGH · 8.7 CVSS v4.0 Published 2026-07-14
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 5 weeks old

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 denial-of-service security issue exists in the affected products. The security issue stems from improper handling of exceptional conditions when processing crafted CIP packets sent to the adapter. A power cycle is required to recover the module and associated I/O.

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

A denial-of-service vulnerability exists in industrial control adapters due to improper handling of exceptional conditions when processing crafted Common Industrial Protocol (CIP) packets. The vulnerability is exploitable remotely via network-based CIP packet injection, causing the affected module to become unresponsive. Recovery requires a physical power cycle, indicating a persistent fault condition likely stemming from memory corruption or a deadlock in the packet processing path.

MitigationApply vendor-supplied patches for affected industrial control adapters when released. Prior to patch availability, isolate affected devices behind firewalls or in dedicated network segments with strict access controls to limit exposure to untrusted CIP 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 device type
    Determine if the target system is an industrial control adapter or PLC that processes Common Industrial Protocol (CIP) traffic. Consult device documentation, inventory records, or network topology to confirm the device category.
    Affected if The device is an industrial control adapter, PLC, or similar industrial device that supports CIP protocol.
  2. Verify CIP service is enabled
    Check if the device has CIP services enabled and listening for network connections. Review device configuration for CIP communication settings, typically on ports 2222, 44818 (Ethernet/IP), or vendor-specific CIP ports. Use network scanning (e.g., nmap) to identify open CIP-related ports.
    Affected if CIP protocol services are enabled and exposed on the network interface.
  3. Assess network exposure
    Determine whether the device with CIP enabled is directly accessible from untrusted networks. Review firewall rules, network segmentation, and access control lists surrounding the industrial device. Check if the CIP port is reachable from external or less-trusted network segments.
    Affected if The CIP-enabled device is accessible from network segments that contain untrusted or external traffic without proper firewall or VLAN isolation.
  4. Compare installed firmware version
    Retrieve the installed firmware or software version from the industrial control device. Consult the device web interface, console, SNMP, or vendor documentation for version retrieval methods. Compare the installed version against any vendor-published affected version ranges.
    Affected if The installed firmware version falls within an affected version range published by the vendor, or no vendor guidance is available to confirm the version is patched.
  5. Check for denial-of-service symptoms
    Monitor for signs of device unresponsiveness, including inability to respond to CIP requests, loss of management connectivity requiring physical power cycle to recover, or logs indicating packet processing failures. Review system logs and network capture for malformed CIP packet errors.
    Affected if The device exhibits persistent unresponsiveness requiring physical power cycle recovery, or logs show CIP packet handling failures.

A user is affected if they operate an industrial control adapter with CIP protocol enabled and exposed to the network, where the installed version matches affected ranges or cannot be confirmed as patched.

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

Apply vendor-supplied patches for affected industrial control adapters when released. Prior to patch availability, isolate affected devices behind firewalls or in dedicated network segments with strict access controls to limit exposure to untrusted CIP traffic.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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