CVE-2026-67873 Memory corruption in n/a

Critical 9.8 Published Updated

A heap-based buffer overflow in lib60870-C allows attackers to execute arbitrary code or cause denial of service via crafted FileSegment ASDU encoding.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-67873?

CVE-2026-67873 is a critical memory corruption vulnerability in n/a, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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

Weakness: CWE-122

Which versions are affected by CVE-2026-67873?

How do I fix CVE-2026-67873?

No fix has been published for CVE-2026-67873 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-67873 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67873 exists.

Sources

Also known as GHSA-vgf8-x653-r7r2.

Is CVE-2026-67873 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free