CVE-2026-21383: Qualcomm AES-GCM Static IV Weakness Affects FastConnect and QCA Chipsets

Technical summary

CVE-2026-21383 is a cryptographic implementation defect affecting AES-GCM key wrapping in Qualcomm chipset firmware. The vulnerability arises from using a static initialization vector instead of generating a unique, non-repeating IV for each encryption operation. AES-GCM security depends on IV uniqueness; reusing an IV with the same key destroys semantic security and allows an adversary to recover the authentication tag pattern and decrypt ciphertext. The issue is classified under CWE-323 (Unprotected Transport of Credentials). Exploitation requires local access and low privileges, indicating the threat model includes compromised applications, local malware, or physical device access scenarios.

Business impact

Organizations deploying affected Qualcomm chipsets in Wi-Fi access points, network infrastructure, IoT devices, or endpoint hardware face exposure of encrypted configuration data, authentication credentials, and inter-device communications. A successful attack could lead to lateral movement within networks, credential theft, configuration manipulation, and regulatory compliance violations (particularly for organizations subject to data protection mandates). Devices in production environments cannot rely on the confidentiality or integrity of cryptographic operations until patched.

Affected systems

The vulnerability impacts a broad range of Qualcomm wireless and networking products, including FastConnect 6900 and 7800 series, QCA (QCA6595AU, QCA6696, QCA6698AQ, QCA6797AQ, QCA8695AU) chipsets, QDU and QDX modem platforms (QDU1000/1110/1210, QDX1010/1011), and various vendor-specific firmware builds (LeMans AU, Pandeiro, QAM series). Both the base chipset hardware and associated firmware images are affected. Organizations should cross-reference their device manifests against this product list, paying particular attention to wireless access points, embedded network devices, and any systems using Qualcomm modems or Wi-Fi connectivity.

Exploitability

The vulnerability has a CVSS 3.1 score of 7.1 (HIGH) with a local attack vector, low attack complexity, and low privilege requirements. It does not require user interaction. Exploitation is feasible for a local attacker (e.g., a compromised app on a device, a malicious service, or physical access) who can observe or interact with the affected encryption operations. The absence of CISA KEV listing does not diminish the intrinsic risk; the cryptographic nature of the flaw means attacks could be mounted offline against captured traffic. No public exploit has been announced, but the straightforward nature of IV reuse vulnerabilities suggests that exploitation could be developed once patching guidance becomes widely available.

Remediation

Apply firmware updates provided by Qualcomm and device manufacturers. Verify patch availability for your specific chipset and hardware variant—many products in the affected list may receive updates through OEM firmware channels rather than direct Qualcomm downloads. For products without available patches, isolate affected devices to restricted network segments and enforce strict access controls. Implement network segmentation to limit local attack surfaces and monitor encrypted traffic patterns for anomalies that could indicate exploitation attempts.

Patch guidance

Contact your device manufacturer or systems integrator for firmware release schedules and patch eligibility. Qualcomm will have published security advisories with specific firmware version numbers; consult those advisories to verify the correct patched version for your hardware revision. Firmware updates typically require controlled deployment and device restarts—coordinate with operational teams to schedule updates during maintenance windows. Test patches in non-production environments first to ensure compatibility with your infrastructure and applications.

Detection guidance

Detection of active exploitation is challenging because the vulnerability involves misuse of encryption rather than network-observable protocol anomalies. However, you can detect the presence of vulnerable firmware through inventory scans (query device firmware versions against known vulnerable builds) and chipset identification. Monitor for unusual patterns in local process behavior that might indicate attempts to access key material or encryption functions. Implement cryptographic integrity monitoring if your devices support remote attestation of firmware state. Log and alert on any unexpected local privilege escalation or unauthorized access to cryptographic subsystems.

Why prioritize this

This vulnerability deserves HIGH priority despite the local-only attack vector because it undermines a fundamental security control—encryption confidentiality and integrity. Organizations that cannot quickly obtain and deploy patches should escalate this into their change management pipelines immediately. The broad range of affected products means many organizations likely have at least one vulnerable device in their inventory. For any system where encrypted data is transmitted or stored, patching this vulnerability is non-deferrable.

Risk score, explained

The CVSS 3.1 score of 7.1 reflects high impact (loss of confidentiality and integrity) combined with moderate exploitability (local access required, but low barriers once access is obtained). The score does not account for the number of affected products or prevalence in real deployments; individual organizations should adjust their risk rating upward if affected devices are business-critical, internet-facing (via management interfaces), or hold sensitive configuration or credential data.

Frequently asked questions