CVE-2026-21385 — 5g Fixed Wireless Access Platform Firmware
HIGHCVE-2026-21385 is a high-severity (CVSS 7.8) CWE-190 vulnerability in qualcomm 5g fixed wireless access platform firmware. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-03-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Memory corruption while using alignments for memory allocation.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-03-03. Federal agencies were required to remediate by 2026-03-24.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-21385.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-21385 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Memory corruption while using alignments for memory allocation.
Affected Products
5g fixed wireless access platform firmwarequalcommapq8098 firmwarequalcommar8031 firmwarequalcommar8035 firmwarequalcommc-v2x 9150 firmwarequalcommcsra6620 firmwarequalcommResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every qualcomm 5g fixed wireless access platform firmware deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2026-21385 yet — track the qualcomm 5g fixed wireless access platform firmware advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-21385 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.