Quick answers
- Is CVE-2026-115723 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115723 being exploited in the wild.
- How severe is CVE-2026-115723?
- High severity, with a CVSS score of 7.4, published 23 October 2026.
- Which products and versions are affected?
- Snap7 through 1.4.3.
- Is there a fix for CVE-2026-115723?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-115723 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115723?
- Check whether you run Snap7 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The passive partner in Snap7 through 1.4.3 fails to validate the BSend total length declared by an active peer, allowing the attacker to declare up to 65535 bytes while sending truncated fragments. A BRecv memcpy operation then writes past the allocated buffer boundary, triggering an out-of-bounds write. The vulnerability requires the attacker to connect from a configured peer address and can result in process crash or memory corruption.
Affected products
- Snap7 through 1.4.3
Timeline
- 2026-10-23: disclosed