Quick answers
- Is CVE-2024-32389 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-32389 being exploited in the wild.
- How severe is CVE-2024-32389?
- Low severity, with a CVSS score of 3.5, published 16 July 2026.
- Which products and versions are affected?
- Kerlink KerOS <= 4.3.3; Kerlink Wirnet iStation 868 <= 4.3.3.
- Is there a fix for CVE-2024-32389?
- 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-2024-32389 attacked?
- It is attacked from the adjacent network, in device firmware.
- Am I affected by CVE-2024-32389?
- Check whether you run Kerlink KerOS or Kerlink Wirnet iStation 868 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
A buffer overflow vulnerability exists in Kerlink KerOS versions 4.3.3 and below, specifically within the SNMP update mechanism. The flaw is rooted in improper input validation (CWE-20) when handling URLs provided for update packages. An attacker located on the same adjacent network can provide a specially crafted URL that triggers memory corruption. This can be leveraged to achieve limited information disclosure. The vendor has indicated that KerOS 4 and 5 are end-of-life and recommends migrating to KerOS 6, which is not affected.
Affected products
- Kerlink KerOS <= 4.3.3
- Kerlink Wirnet iStation 868 <= 4.3.3
Timeline
- 2024-03-19: disclosed: Vulnerability reported to vendor
- 2024-03-29: other: Vendor confirmed vulnerability
- 2025-09-06: other: Vendor declared KerOS 4 End-of-Life (EOL)
- 2026-05-27: advisory: Public disclosure by BDO Security