dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-26048

HIGH · 7.5 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The Wi-Fi router is vulnerable to de-authentication attacks due to the absence of management frame protection, allowing forged deauthentication and disassociation frames to be broadcast without authentication or encryption. An attacker can use this to cause unauthorized disruptions and create a denial-of-service condition.

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 · high confidence

The Wi-Fi router lacks IEEE 802.11w management frame protection (MFP), allowing attackers to forge and broadcast deauthentication and disassociation frames without authentication or encryption. This enables unauthorized denial-of-service attacks by disconnecting legitimate clients from the network.

MitigationEnable management frame protection (802.11w/MFP) on the Wi-Fi router and ensure all connected wireless clients support this standard to prevent forged management frame attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if the router supports 802.11w/MFP
    Access the router's web administration interface or CLI and navigate to the Wireless Security or Wi-Fi settings section. Look for options labeled '802.11w', 'Management Frame Protection', 'MFP', or 'Protected Management Frames'. Determine whether this feature exists in the available options.
    Affected if The router's wireless settings do not list or expose any 802.11w or MFP configuration option, meaning the feature is not implemented.
  2. Verify if 802.11w/MFP is enabled
    In the router's wireless security settings, locate the 802.11w/MFP setting and confirm its current state. It is typically set to 'Disabled', 'Optional', or 'Required'. Check both the 2.4GHz and 5GHz band configurations if separate settings exist.
    Affected if The 802.11w/MFP setting is found but set to 'Disabled' or is not explicitly set to 'Required'.
  3. Inspect wireless client association for MFP capability
    Use the router's status page, connected clients list, or a wireless sniffer tool to examine the capabilities of currently associated wireless clients. Look for indication of 'MFP' or '802.11w' in the client capability information.
    Affected if Connected clients show no MFP capability indicators and the router is not enforcing MFP as mandatory.
  4. Check for unauthenticated deauthentication frame reception
    Use a wireless monitoring tool (such as airodump-ng, Wireshark, or the router's event logs) to capture or observe wireless management frames on the network. Monitor for frequent deauthentication or disassociation frames that appear to originate from legitimate access points but were not triggered by legitimate disconnections.
    Affected if A high volume of deauthentication/disassociation frames is observed on the network without corresponding user-initiated disconnections, suggesting the lack of frame protection allows forged frames to be processed.

The environment is affected if the router does not support or have 802.11w/MFP enabled in its wireless security configuration, allowing forged deauthentication frames to disconnect clients without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable management frame protection (802.11w/MFP) on the Wi-Fi router and ensure all connected wireless clients support this standard to prevent forged management frame attacks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26048 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26048 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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