CVE-2026-67873: n/a
CVE-2026-67873 is a heap-based buffer overflow vulnerability in lib60870-C version 2.4.0. It occurs in the server-side FileSegment ASDU encoding path due to improper validation of the residual capacity of the ASDU frame before encoding. This flaw allows the encoding function to write beyond the allocated buffer.
AI Analysis
Technical Summary
This vulnerability exists in lib60870-C 2.4.0 within the FileSegment_encode() function used on the server side. The function only validates the standalone segment length using FileSegment_GetMaxDataSize() but fails to check the remaining capacity of the current ASDU frame before encoding object fields and segment data. This can lead to a heap-based buffer overflow condition.
Potential Impact
A heap-based buffer overflow can potentially lead to memory corruption, which may cause application crashes or enable an attacker to execute arbitrary code if exploited. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using lib60870-C version 2.4.0 in environments where untrusted input could trigger this vulnerability.
CVE-2026-67873: n/a
Description
CVE-2026-67873 is a heap-based buffer overflow vulnerability in lib60870-C version 2.4.0. It occurs in the server-side FileSegment ASDU encoding path due to improper validation of the residual capacity of the ASDU frame before encoding. This flaw allows the encoding function to write beyond the allocated buffer.
Affected software
pkg:github/mz-automation/lib60870Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability exists in lib60870-C 2.4.0 within the FileSegment_encode() function used on the server side. The function only validates the standalone segment length using FileSegment_GetMaxDataSize() but fails to check the remaining capacity of the current ASDU frame before encoding object fields and segment data. This can lead to a heap-based buffer overflow condition.
Potential Impact
A heap-based buffer overflow can potentially lead to memory corruption, which may cause application crashes or enable an attacker to execute arbitrary code if exploited. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using lib60870-C version 2.4.0 in environments where untrusted input could trigger this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- mitre
- Date Reserved
- 2026-07-30T00:00:00.000Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a73c6b4bf8831d5399d0b90
Added to database: 08/05/2026, 23:26:44 UTC
Last enriched: 08/05/2026, 23:44:54 UTC
Last updated: 08/05/2026, 23:51:18 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.