CVE-2026-21383
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 · uneditedCryptographic Issue when using a static initialization vector for AES-GCM key wrapping, which requires a unique value for each call to ensure security.
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 confidenceThe vulnerability stems from AES-GCM key wrapping using a static initialization vector (IV) instead of generating a unique IV for each encryption operation. When the same IV is reused with AES-GCM, it compromises the confidentiality of the encrypted data by allowing attackers to deduce relationships between plaintexts, violating the fundamental requirement of GCM mode that each IV must be unique for a given key.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device or component using Qualcomm firmwareReview system documentation, device inventory, or network device listings to determine if the hardware incorporates any of the affected Qualcomm firmware components (Fastconnect 6900/7800, Lemans, Pandeiro, Qam series)Affected if The device or component uses any of the listed Qualcomm firmware products
-
Determine the firmware version installedAccess the device management interface, firmware update system, or use vendor-specific commands (such as 'show version', 'get firmware version', or checking /proc/version on embedded systems) to retrieve the installed firmware versionAffected if Any version of the affected Qualcomm firmware is installed (all versions are vulnerable)
-
Confirm AES-GCM key wrapping is in useReview application or system configuration files, cryptographic library settings, or code references to identify if AES-GCM mode is being used for key wrapping operationsAffected if AES-GCM mode is enabled and used for encrypting/wrapping keys
-
Inspect IV generation configurationExamine configuration files, cryptographic policy settings, or key management logs to determine how initialization vectors are generated for AES-GCM operations. Look for patterns indicating reuse or static IV valuesAffected if A static, reused, or non-unique IV is configured or observed in AES-GCM key wrapping operations
A system is affected if it uses any of the listed Qualcomm firmware products with AES-GCM key wrapping and the IV is static or reused across operations.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace the static IV with cryptographically random unique IV generation for each key wrapping operation, ensuring proper IV handling (typically 12 bytes for GCM) and secure storage/transmission of the IV alongside the ciphertext.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21383 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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