Secuno
ENNL
Book demo

CVE-2026-67873

Buffer overflow

9.8 CRITICALEPSS 0.73%
  1. Published5 Aug 2026

Description

A heap-based buffer overflow exists in lib60870-C 2.4.0 in the server-side FileSegment ASDU encoding path. The issue occurs because FileSegment_encode() validates only the standalone segment length via FileSegment_GetMaxDataSize() and does not verify the residual capacity of the current ASDU frame before encoding object fields and segment data

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-148888.1
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0…
CVE-2026-142699.8
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0…
CVE-2026-764719.8
A vulnerability in the NX-API feature of Cisco NX-OS Software could allow an…
CVE-2026-465708.1
In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_index_walk_down() in…
CVE-2026-1062928.3
Buffer overflow in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote…
CVE-2026-1062478.3
Buffer overflow in ANGLE in Google Chrome prior to 155.0.8059.39 allowed a remote…

Frequently asked

Is CVE-2026-67873 being actively exploited?

CVE-2026-67873 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.73%.

How severe is CVE-2026-67873?

CVE-2026-67873 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.73% probability of exploitation.

How do I fix CVE-2026-67873?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-67873 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.