{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-7763 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7763 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7763 is a critical memory corruption vulnerability in Morse Micro HaLowLink 2, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7763 and fix it if it is affected.\n\nWhat it is: CVE-2026-7763 is a critical memory corruption vulnerability in Morse Micro HaLowLink 2, published on 5 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-7763 in the wild and no public exploit code.\n\nAffected product: Morse Micro HaLowLink 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7763/ (Markdown: https://insights.sbomify.com/CVE-2026-7763/index.md)","id":"CVE-2026-7763","markdown":"https://insights.sbomify.com/CVE-2026-7763/index.md","name":"CVE-2026-7763","record":{"aliases":["GHSA-wq9p-qhjj-gw6h"],"analysis":{"component_type":"kernel","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"HaLow Wi-Fi driver","requires_auth":"none","summary":"Unauthenticated attackers can cause kernel panic or execute code via crafted beacon frames in the Morse Micro HaLowLink 2 Wi-Fi driver.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bugcrowd","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"A heap-based buffer overflow vulnerability in the morse.ko HaLow Wi-Fi kernel driver in Morse Micro HaLowLink 2 software versions prior to 2.11.13 allows an unauthenticated attacker within radio range to cause a Denial of Service (kernel panic) or potentially achieve Remote Code Execution via a crafted 802.11ah beacon frame containing a malformed Traffic Indication Map (TIM) Information Element. The function morse_page_slicing_process_tim_element() in page_slicing.c derives the TIM bitmap length directly from a received IE field without validating it against the fixed-size destination buffer before passing it to memset and memcpy operations, allowing up to 252 bytes of attacker-controlled data to be written beyond the buffer boundary. Because beacons are broadcast frames processed during passive scanning, no authentication, association, or user interaction is required.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Heap buffer overflow in morse.ko TIM IE processing","id":"CVE-2026-7763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Out-of-bounds read in morse.ko Vendor IE processing","id":"CVE-2026-7764"},"packages":[],"prev":{"headline":"Heap buffer overflow in dot11ah.ko S1G Capabilities IE processing","id":"CVE-2026-7762"},"products":["HaLowLink 2"],"published":"2026-06-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-05","vendors":["Morse Micro"]},"summary":"Unauthenticated attackers can cause kernel panic or execute code via crafted beacon frames in the Morse Micro HaLowLink 2 Wi-Fi driver.","url":"https://insights.sbomify.com/CVE-2026-7763/"}