CVE-2025-27066
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTransient DOS while processing an ANQP message.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA transient denial-of-service vulnerability exists in the processing of ANQP (Access Network Query Protocol) messages, which are used in IEEE 802.11u Wi-Fi networks for interworking and hotspot roaming. An attacker can send specially crafted ANQP messages to cause a temporary service disruption on affected Wi-Fi access points or controllers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Wi-Fi access point or controller firmwareLog into the device management console or check the device firmware information page. Look for the firmware version string which typically appears in system info, status, or about pages. Common locations: Web UI under 'Status' or 'Management' > 'Firmware Version', CLI command like 'show version' or 'get firmwarever', or check the device label/documentation.Affected if The firmware matches one of these: Qualcomm 315 5g Iot Modem, Qualcomm Aqt1000, Qualcomm Ar8031, Qualcomm Ar8035, Qualcomm Ar9380, Qualcomm Qcn5021, Qualcomm Qcn5022, or Qualcomm Qcn5024
-
Check if IEEE 802.11u interworking is enabledAccess the wireless configuration settings on the access point or controller. Look for settings named 'Interworking', '802.11u', 'Hotspot 2.0', 'HS2.0', 'Wi-Fi Alliance Passpoint', or 'ANQP' in the wireless network profile or SSID configuration. Verify whether these features are turned on or enabled.Affected if Interworking, 802.11u, Hotspot 2.0, or ANQP features are enabled on any SSID or wireless profile
-
Verify ANQP query processing is activeIf available, check the device logs or debug settings for ANQP-related entries. In the wireless configuration, look for options controlling ANQP response capability orvenue, NAI realm, or cellular banner queries. Confirm whether the device accepts and processes ANQP queries from clients.Affected if The device is configured to process ANQP queries from connecting clients (default behavior when interworking is enabled)
If your Wi-Fi access point or controller uses any of the listed Qualcomm firmware variants AND has 802.11u interworking or ANQP features enabled, your environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-provided patches or firmware updates for Wi-Fi infrastructure devices; if patches are unavailable, consider network segmentation or disabling interworking features to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27066 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27066 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data