CVE-2026-12818
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 · uneditedDelta Electronics DVP12SE PLCs are susceptible to a resource allocation vulnerability without limits or throttling (CWE-770) within their Modbus TCP service.
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 confidenceDelta Electronics DVP12SE PLCs contain a resource allocation vulnerability (CWE:770) in their Modbus TCP service that allows unlimited or unthrottled resource consumption, potentially enabling denial-of-service conditions or resource exhaustion attacks against the PLC.
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:H/VI:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm PLC model is DVP12SEIdentify the PLC device model through its labeling, web interface, or management console. Cross-reference with device documentation or inventory records.Affected if The device is a Delta Electronics DVP12SE PLC
-
Verify Modbus TCP service is enabledAccess the PLC programming software (such as Delta DVP Studio) or the PLC web management interface. Check the Modbus TCP service configuration settings to confirm the service is actively listening on port 502.Affected if Modbus TCP service is enabled and running on the PLC
-
Check Modbus TCP port network exposureUse network scanning tools (such as nmap) or review firewall rules to determine if port 502/TCP is accessible from network segments outside the local control system zone.Affected if Modbus TCP port 502 is exposed to untrusted or external network segments
-
Monitor resource consumptionReview PLC performance metrics through its management interface or external monitoring tools. Check CPU usage, memory utilization, and network bandwidth consumption during Modbus TCP communication cycles.Affected if Abnormally high or unbounded resource consumption is observed during Modbus TCP operations
-
Check for rate limiting configurationExamine the PLC network configuration or any intermediate network devices for rate limiting, traffic shaping, or throttling settings applied to Modbus TCP traffic.Affected if No rate limiting or throttling mechanism is configured for Modbus TCP communications
A user is affected if they operate a DVP12SE PLC with Modbus TCP service enabled and accessible, particularly on networks without rate limiting protections in place.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement network segmentation to isolate PLCs from untrusted networks, apply rate limiting or traffic shaping on Modbus TCP communications, and monitor for anomalous traffic patterns indicating resource exhaustion attempts.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
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 locallyCheck whether your project pulls in CVE-2026-12818 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12818 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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