dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20646

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-03
Fix available
A fix is available. Upgrade to 7.6.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In wlan AP FW, there is a possible out of bounds write due to improper input validation. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00389074; Issue ID: MSV-1803.

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

A critical out-of-bounds write vulnerability exists in WLAN Access Point firmware due to improper input validation. This memory corruption flaw allows remote attackers to escalate privileges without any user interaction, potentially giving them full control over the affected AP device.

MitigationApply vendor firmware patch WCNCR00389074 to all affected WLAN Access Point devices as soon as possible. Given the CVSS 9.8 severity and remote exploitability, this should be prioritized as an emergency patch deployment.

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 data
Software Development KitApplication
Affected:< 7.6.7.2

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify Mediatek WLAN AP firmware in use
    Check the device firmware documentation, boot logs, or system information to confirm the WLAN Access Point uses Mediatek Software Development Kit. Look for Mediatek SDK references or WCN-series chipset identifiers in the device specifications.
    Affected if The device firmware is built on or includes Mediatek SDK components for WLAN Access Point functionality.
  2. Determine installed Mediatek SDK version
    Access the device command line or firmware metadata and locate the SDK version file or build information. Common paths include /etc/version, /var/log/boot.log, or firmware release notes. Run 'cat /etc/version' or 'grep -i mediatek /var/log/messages' if available.
    Affected if The SDK version is lower than 7.6.7.2 (e.g., 7.6.6.x, 7.5.x, or earlier).
  3. Verify WLAN Access Point feature is enabled
    Check if the wireless AP functionality is actively configured on the device. Use 'iwconfig' or 'wlanconfig' commands to list active wireless interfaces, or check the web UI/admin panel for enabled wireless access point profiles.
    Affected if WLAN Access Point interfaces are present and configured, making the vulnerable code path reachable.
  4. Assess network exposure of management interface
    Review the device network configuration to determine if the WLAN AP management interface is accessible from untrusted networks. Check firewall rules, access control lists, or WAN-facing interface bindings using 'iptables -L' or the device admin interface.
    Affected if The AP management or control plane is exposed to external networks without proper isolation, allowing remote exploitation.

The environment is affected if the device runs Mediatek WLAN AP firmware built with SDK version below 7.6.7.2 and has the access point feature enabled and network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 7.6.7.2 or later
Fixed in 7.6.7.2
Interim mitigation

Apply vendor firmware patch WCNCR00389074 to all affected WLAN Access Point devices as soon as possible. Given the CVSS 9.8 severity and remote exploitability, this should be prioritized as an emergency patch deployment.

Recommended fix High confidence

Software Development Kit 7.6.7.2 or later

  1. Obtain MediaTek Software Development Kit version 7.6.7.2 or later from the official MediaTek source (corp.mediatek.com)
  2. Apply the SDK upgrade following the standard MediaTek upgrade procedure for your environment
  3. Verify the installed SDK version is 7.6.7.2 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20646 — 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-2025-20646 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