CVE-2026-6458

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

No CVSS.

References

Link	Resource
https://github.com/chipsalliance/caliptra-sw/security/advisories/GHSA-834g-h5x6-2hqr

Configurations

No configuration.

History

24 Jun 2026, 00:16

Type	Values Removed	Values Added
New CVE

Information

Published : 2026-06-24 00:16

Updated : 2026-06-25 16:14

NVD link : CVE-2026-6458

Mitre link : CVE-2026-6458

CVE.ORG link : CVE-2026-6458

JSON object : View

Products Affected

No product.

CWE

CWE-325

Missing Cryptographic Step

{"id": "CVE-2026-6458", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-6458", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-06-24T13:14:19.562293Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "b01ddd03-5ef6-483b-b2c5-acba77f1a554", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.1, "Automatable": "NOT_DEFINED", "attackVector": "ADJACENT", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "LOW", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "LOW", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "b01ddd03-5ef6-483b-b2c5-acba77f1a554", "affectedData": [{"vendor": "Caliptra", "modules": ["aes_256_gcm_update"], "product": "Core Runtime Firmware", "versions": [{"status": "affected", "version": "2.0.0", "versionType": "semver", "lessThanOrEqual": "2.0.1"}, {"status": "affected", "version": "2.1.0", "versionType": "semver"}, {"status": "unaffected", "version": "2.0.2", "versionType": "semver"}, {"status": "unaffected", "version": "2.1.1", "versionType": "semver"}], "packageName": "Core Runtime Firmware", "collectionURL": "https://github.com/chipsalliance/caliptra-sw", "defaultStatus": "unaffected"}]}], "published": "2026-06-24T00:16:34.037", "references": [{"url": "https://github.com/chipsalliance/caliptra-sw/security/advisories/GHSA-834g-h5x6-2hqr", "source": "b01ddd03-5ef6-483b-b2c5-acba77f1a554"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "b01ddd03-5ef6-483b-b2c5-acba77f1a554", "description": [{"lang": "en", "value": "CWE-325"}]}], "descriptions": [{"lang": "en", "value": "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.\n\nThis issue affects Core Runtime Firmware: from 2.0.0 through 2.0.1, 2.1.0."}], "lastModified": "2026-06-25T16:14:14.483", "sourceIdentifier": "b01ddd03-5ef6-483b-b2c5-acba77f1a554"}