Is CVE-2026-7763 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-7763 being exploited in the wild.

How severe is CVE-2026-7763?

Informational severity, with a CVSS score of 8.8, published 5 June 2026.

Which products and versions are affected?

Morse Micro HaLowLink 2 prior to 2.11.13.

Is there a fix for CVE-2026-7763?

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-7763 attacked?

It is attacked from the adjacent network, in device firmware.

Am I affected by CVE-2026-7763?

Check whether you run Morse Micro HaLowLink 2 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.

CVE-2026-7763: Morse Micro HaLowLink 2 heap overflow in morse.ko kernel driver

CVE-2026-7763 · Severity: info · CVSS 8.8 · Published 2026-06-05

A security vulnerability exists in the Morse Micro HaLow Wi-Fi driver, which is used to provide long-range wireless connectivity for IoT devices. An attacker within radio range can send a specially crafted Wi-Fi signal to crash the device or potentially take full control of it. This attack requires no user interaction and can be performed even if the attacker is not logged into the network, potentially leading to service outages or unauthorized access to device data.

Technologies: Morse Micro HaLowLink 2. Vendors: Morse Micro.

Quick answers

Is CVE-2026-7763 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-7763 being exploited in the wild.
How severe is CVE-2026-7763?: Informational severity, with a CVSS score of 8.8, published 5 June 2026.
Which products and versions are affected?: Morse Micro HaLowLink 2 prior to 2.11.13.
Is there a fix for CVE-2026-7763?: 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-7763 attacked?: It is attacked from the adjacent network, in device firmware.
Am I affected by CVE-2026-7763?: Check whether you run Morse Micro HaLowLink 2 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 heap-based buffer overflow exists in the morse.ko HaLow Wi-Fi kernel driver within the morse_page_slicing_process_tim_element() function in page_slicing.c. The vulnerability is caused by the driver deriving the Traffic Indication Map (TIM) bitmap length directly from a received Information Element (IE) field without validating it against the fixed-size destination buffer. This allows an attacker to trigger memset and memcpy operations that write up to 252 bytes of controlled data beyond the buffer boundaries. The attack is delivered via a crafted 802.11ah beacon frame and is processed during passive scanning, meaning no authentication or association is required. This can result in a Denial of Service (kernel panic) or Remote Code Execution (RCE). The issue is resolved in HaLowLink 2 software version 2.11.13.

Affected products

Morse Micro HaLowLink 2 software prior to 2.11.13

Timeline

2026-06-05: disclosed
2026-06-05: advisory

References

https://www.morsemicro.com/security-advisories/MM-SA-2026-001

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.