CVE-2026-51219
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 · uneditedA heap buffer overflow in the HighPriorityASDUQueue_hasUnconfirmedIMessages function of lib60870 v2.3.3 to v2.3.6 allows attackers to cause a Denial of Service (DoS) via a crafted payload.
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 confidenceA heap buffer overflow vulnerability exists in lib60870 versions 2.3.3 through 2.3.6 within the HighPriorityASDUQueue_hasUnconfirmedIMessages function. Attackers can trigger a denial of service by sending a specially crafted payload that overflows a heap-allocated buffer.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed lib60870 versionCheck the version of lib60870 installed in your environment. Common methods: check your dependency manifest (package.json, requirements.txt, CMakeLists.txt), run 'ls -la' on the library file, or query the library at runtime if your application exposes version info. Compare the version number to the affected range 2.3.3 through 2.3.6.Affected if The installed version falls within 2.3.3 to 2.3.6 inclusive.
-
Determine if IEC 60870-5-104 server mode is enabledReview your application configuration and code to determine if the IEC 60870-5-104 protocol server (CS104 Server) is instantiated and listening for incoming connections. Check for initialization of CS104 Server objects and binding to TCP port 2404 (default).Affected if Your application runs as an IEC 60870-5-104 server accepting client connections.
-
Verify HighPriorityASDUQueue usage in application logicInspect your source code or binary for usage of the HighPriorityASDUQueue_hasUnconfirmedIMessages function or related ASDU queue handling code. This function processes incoming ASDU messages.Affected if Your application processes ASDU messages from IEC 60870-5-104 clients using the queue mechanism.
You are affected if you are running lib60870 version 2.3.3, 2.3.4, 2.3.5, or 2.3.6 AND your application operates as an IEC 60870-5-104 server that processes ASDU messages from clients.
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 dataUpgrade lib60870 to version v2.3.7 or later which contains the patch for this vulnerability. If upgrade is not immediately possible, implement input validation and rate limiting on incoming IEC 60870-5-104 connections to reduce attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-51219 — 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-51219 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