Is CVE-2026-6458 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-6458 being exploited in the wild.

How severe is CVE-2026-6458?

Informational severity, with a CVSS score of 5.1, published 24 June 2026.

Which products and versions are affected?

Caliptra Core Runtime Firmware 2.0.0, 2.0.1, 2.1.0.

Is there a fix for CVE-2026-6458?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-6458 attacked?

It is attacked from the adjacent network, in device firmware.

Am I affected by CVE-2026-6458?

Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-6458: Caliptra Core Firmware missing cryptographic step in aes_256_gcm_update

CVE-2026-6458 · Severity: info · CVSS 5.1 · Published 2026-06-24

Caliptra Core Runtime Firmware, which provides secure silicon root-of-trust functions, contains a flaw in its cryptographic processing module. When certain encryption tasks are performed without additional authenticated data, the system fails to properly verify the integrity of the first block of data. This allows an attacker with local network access to modify parts of the encrypted information without the system detecting the tampering, potentially compromising the security of the protected device.

Quick answers

Is CVE-2026-6458 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-6458 being exploited in the wild.
How severe is CVE-2026-6458?: Informational severity, with a CVSS score of 5.1, published 24 June 2026.
Which products and versions are affected?: Caliptra Core Runtime Firmware 2.0.0, 2.0.1, 2.1.0.
Is there a fix for CVE-2026-6458?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-6458 attacked?: It is attacked from the adjacent network, in device firmware.
Am I affected by CVE-2026-6458?: Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in the Caliptra Core Runtime Firmware within the `aes_256_gcm_update()` function of the `drivers/src/aes.rs` module. When the streaming AES-256-GCM API is invoked with empty Authenticated Additional Data (AAD), the hardware GHASH accumulator state is not saved after the initial update call. This causes the final authentication tag to exclude the first batch of processed ciphertext. An attacker with 'Low' privileges and 'Adjacent' network access can exploit this to modify the first batch of ciphertext without triggering an authentication failure. The issue is fixed in versions 2.0.2 and 2.1.1.

Affected products

Caliptra Core Runtime Firmware 2.0.0, 2.0.1, 2.1.0

Timeline

2026-06-23: disclosed: GHSA-834g-h5x6-2hqr published
2026-06-24: advisory: NVD published CVE-2026-6458

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.