CVE-2026-6458: CWE-325 Missing Cryptographic Step in Caliptra Core Runtime Firmware
Missing cryptographic step in Caliptra Core Firmware (aes_256_gcm_update module) results in an incorrect GCM authentication tag. When the streaming AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator state is not saved after the first update call, causing the final tag to exclude the first batch of processed ciphertext. Ciphertext produced by that call may be modified without the tag reflecting the change. This issue affects Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0.
AI Analysis
Technical Summary
The vulnerability in Caliptra Core Runtime Firmware's aes_256_gcm_update module arises from a missing cryptographic step that leads to an incorrect GCM authentication tag. Specifically, when the streaming AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator state is not preserved after the first update call. Consequently, the final authentication tag excludes the first batch of processed ciphertext, enabling undetected modifications to that ciphertext portion. This affects firmware versions 2.0.0 through 2.0.1 and 2.1.0.
Potential Impact
An attacker with low privileges and network access could modify ciphertext processed by the vulnerable AES-256-GCM implementation without detection, due to the incorrect authentication tag. This undermines the integrity guarantees of the cryptographic operation, potentially allowing tampering with encrypted data. However, the vulnerability does not allow privilege escalation or denial of service directly and requires specific conditions (empty AAD and use of streaming API).
Mitigation Recommendations
No official fix or patch is currently available for this vulnerability. Users should monitor the vendor's advisory for updates regarding remediation. Until a fix is provided, avoid using the streaming AES-256-GCM API with empty AAD in the affected firmware versions if possible.
CVE-2026-6458: CWE-325 Missing Cryptographic Step in Caliptra Core Runtime Firmware
Description
Missing cryptographic step in Caliptra Core Firmware (aes_256_gcm_update module) results in an incorrect GCM authentication tag. When the streaming AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator state is not saved after the first update call, causing the final tag to exclude the first batch of processed ciphertext. Ciphertext produced by that call may be modified without the tag reflecting the change. This issue affects Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0.
CVSS v4.0
Score 5.1medium
Affected software
pkg:github/Core Runtime FirmwareRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Caliptra Core Runtime Firmware's aes_256_gcm_update module arises from a missing cryptographic step that leads to an incorrect GCM authentication tag. Specifically, when the streaming AES-256-GCM API is used with empty AAD, the hardware GHASH accumulator state is not preserved after the first update call. Consequently, the final authentication tag excludes the first batch of processed ciphertext, enabling undetected modifications to that ciphertext portion. This affects firmware versions 2.0.0 through 2.0.1 and 2.1.0.
Potential Impact
An attacker with low privileges and network access could modify ciphertext processed by the vulnerable AES-256-GCM implementation without detection, due to the incorrect authentication tag. This undermines the integrity guarantees of the cryptographic operation, potentially allowing tampering with encrypted data. However, the vulnerability does not allow privilege escalation or denial of service directly and requires specific conditions (empty AAD and use of streaming API).
Mitigation Recommendations
No official fix or patch is currently available for this vulnerability. Users should monitor the vendor's advisory for updates regarding remediation. Until a fix is provided, avoid using the streaming AES-256-GCM API with empty AAD in the affected firmware versions if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Caliptra
- Date Reserved
- 2026-04-16T21:11:47.086Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3b23adeed863c81ed4a4b5
Added to database: 06/24/2026, 00:24:13 UTC
Last enriched: 06/24/2026, 00:39:23 UTC
Last updated: 08/06/2026, 12:41:12 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.