Qca2066 vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

Qca2066 is made by Qualcomm. We track 85 published vulnerabilities listed under that exact name, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 3 June 2025. Qualcomm lists newer releases under their own names, such as Qca2066 Firmware, so check those pages too.

Check your version

The most recent Qca2066 flaw added to the known-exploited list is CVE-2025-27038, on 3 June 2025. We keep watching the known-exploited list.

Other names

Is Qca2066 listed under other names? Yes.

Qualcomm also lists Qca2066 under more specific names, such as Qca2066 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.

Versions

Which versions of Qca2066 do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

Known exploited

Which Qca2066 vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.5
    CVE-2025-27038HighKnown exploited
    Qualcomm Multiple Chipsets Use-After-Free Vulnerability

    Multiple Qualcomm chipsets contain a use-after-free vulnerability.

    Chance of use1.0%Known exploited since3 Jun 2025
Exploit likelihood

Which Qca2066 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.

50% or more10% to 49%Under 10%
  1. 13%

    Improper authentication of Non-EAPOL/WAPI plaintext frames during four-way handshake can lead to arbitrary network packet injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer...

    CVSS9.8Published8 Sep 2021
  2. 1.0%
    CVE-2025-27038HighKnown exploited

    Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.

    CVSS7.5Published3 Jun 2025
  3. 0.9%

    Out of bound read occurs while processing crafted SDP due to lack of check of null string in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS9.1Published7 Apr 2021
  4. 0.8%

    Denial of service in WLAN due to out-of-bound read happens while processing VHT action frame in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS7.5Published19 Oct 2022
  5. 0.8%

    Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity

    CVSS9.8Published12 Nov 2021
  6. 0.7%

    Improper authentication of EAP WAPI EAPOL frames from unauthenticated user can lead to information disclosure in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS7.5Published20 Oct 2021
  7. 0.6%

    Possible buffer out of bound read can occur due to improper validation of TBTT count and length while parsing the beacon response in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics...

    CVSS9.1Published20 Oct 2021
  8. 0.6%

    Possible buffer over read due to lack of length check while parsing beacon IE response in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS9.1Published20 Oct 2021
  9. 0.6%

    Possible denial of service scenario due to improper handling of group management action frame in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon...

    CVSS7.5Published7 May 2021
  10. 0.6%

    Possible assertion due to lack of physical layer state validation in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon...

    CVSS7.5Published9 Sep 2021
Precursor Intelligence

Running Qca2066? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 85 published vulnerabilities listed under the name Qca2066, across 0 versions. The most recent Qca2066 flaw added to the known-exploited list is CVE-2025-27038, on 3 June 2025.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2025-27038.

Qualcomm also lists Qca2066 under more specific names, such as Qca2066 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 Qca2066. 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.