Mt7663 vulnerabilitiesRanked by how likely they are to be used.
Mt7663 is made by Mediatek. We track 46 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Mediatek lists newer releases under their own names, such as Mt7663 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is Mt7663 listed under other names? Yes.
Mediatek also lists Mt7663 under more specific names, such as Mt7663 Firmware. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Mt7663 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Mt7663's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Mt7663 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.8%CVE-2022-32589High
In Wi-Fi driver, there is a possible way to disconnect Wi-Fi due to an improper resource release.
- 0.5%CVE-2023-32820High
In wlan firmware, there is a possible firmware assertion due to improper input handling.
- 0.3%CVE-2022-32655Medium
In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling.
- 0.3%CVE-2022-32656Medium
In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling.
- 0.3%CVE-2022-32654Medium
In Wi-Fi driver, there is a possible undefined behavior due to incorrect error handling.
- 0.3%CVE-2022-20023Medium
In Bluetooth, there is a possible application crash due to bluetooth flooding a device with LMP_AU_rand packet.
- 0.3%CVE-2022-20022Medium
In Bluetooth, there is a possible link disconnection due to bluetooth does not properly handle a connection attempt from a host with the same BD address as the currently connected BT host.
- 0.3%CVE-2022-20021Medium
In Bluetooth, there is a possible application crash due to bluetooth does not properly handle the reception of multiple LMP_host_connection_req.
- 0.2%CVE-2025-20649Medium
In Bluetooth Stack SW, there is a possible information disclosure due to a missing permission check.
- 0.2%CVE-2025-20748Medium
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check.
Running Mt7663? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In Wi-Fi driver, there is a possible way to disconnect Wi-Fi due to an improper resource release. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07030600; Issue ID: ALPS07030600.
- Matched to
- Mt7663 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 46 published vulnerabilities listed under the name Mt7663, across 0 versions.
None of Mt7663's vulnerabilities is on the list of flaws known to be exploited today.
Mediatek also lists Mt7663 under more specific names, such as Mt7663 Firmware. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Mt7663. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.