CVE-2020-11269

Possible memory corruption while processing EAPOL frames due to lack of validation of key length...

8.8 High

Possible memory corruption while processing EAPOL frames due to lack of validation of key length before using it in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Attack profile

How easy it is to exploit

Attack vector: Adjacent network
Complexity: Low
Privileges needed: None
User interaction: None

What an attacker can affect

Confidentiality: High
Integrity: High
Availability: High

Exploit likelihood

0.29%Unchanged since Apr 14, 2021

What each source reports

NVD Score used 8.8

Record: CVE-2020-11269
CVSS 3.1: 8.8 HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.0: 8.3 HighAV:A/AC:L/Au:N/C:C/I:C/A:C
Weakness: CWE-190
Updated: 2026-11-02

CVE List No score

Record: CVE-2020-11269
Updated: 2026-11-02

EUVDEUVD-2020-3623 No score

Record: EUVD-2020-3623
Updated: 2026-11-03

GitHub AdvisoriesGHSA-wq76-jv4p-3h98 No score

Possible memory corruption while processing EAPOL frames due to lack of validation of key length...

Record: GHSA-wq76-jv4p-3h98
Weakness: CWE-190
Updated: 2026-11-02

Affected products

Show 526 moreShow less

History

History
Recorded	Changed	Sources
Nov 3, 2026	aliases	EUVD
Nov 2, 2026	first indexed	CVE List, GitHub Advisories, NVD

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2020-11269 is a high vulnerability (CVSS 8.8) in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer Iot, Snapdragon Industrial Iot, Snapdragon Iot, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure And Networking, published February 22, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.29%, the 22nd percentile. No source names a fixed version.