How severe is CVE-2026-21385?

CVE-2026-21385 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-21385?

Affected package information for CVE-2026-21385 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-21385?

No fixed version has been published for CVE-2026-21385 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2026-21385 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-21385 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-21385?

CVE-2026-21385 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2026-21385 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2026-21385 (Qualcomm Multiple Chipsets Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-03-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-03-24. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2026-21385?

CVE-2026-21385 is classified as CWE-190 (CWE-190). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2026-21385?

CVE-2026-21385 affects qualcomm 5g fixed wireless access platform firmware; qualcomm apq8098 firmware; qualcomm ar8031 firmware; qualcomm ar8035 firmware, and 233 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-21385 published, and has it been updated?

CVE-2026-21385 was published on March 2, 2026 and was last updated on March 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-03-03 — agencies required to remediate by 2026-03-24

CVE-2026-21385

HIGH

Memory corruption while using alignments for memory allocation.

Published

Mar 2, 2026

Updated

Mar 4, 2026

Affected

0 pkgs

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk46th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Memory corruption while using alignments for memory allocation.

Affected Products

237 products · 237 configurations

5g fixed wireless access platform firmwarequalcomm

all

apq8098 firmwarequalcomm

all

ar8031 firmwarequalcomm

all

ar8035 firmwarequalcomm

all

c-v2x 9150 firmwarequalcomm

all

csra6620 firmwarequalcomm

all

Frequently Asked Questions

Memory corruption while using alignments for memory allocation.

O3 Security · Impact-Aware SCA

Is CVE-2026-21385 in your stack?

O3 detects CVE-2026-21385 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works