{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-3337", "assignerOrgId": "ff89ba41-3aa1-4d27-914a-91399e9639e5", "state": "PUBLISHED", "assignerShortName": "AMZN", "dateReserved": "2026-02-27T15:16:28.371Z", "datePublished": "2026-03-02T21:20:08.532Z", "dateUpdated": "2026-03-03T20:04:27.577Z" }, "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "AWS-LC", "vendor": "AWS", "versions": [ { "lessThan": "1.69.0", "status": "affected", "version": "1.21.0", "versionType": "custom" } ] }, { "defaultStatus": "unaffected", "product": "AWS-LC-FIPS", "vendor": "AWS", "versions": [ { "lessThan": "3.2.0", "status": "affected", "version": "3.0.0", "versionType": "custom" } ] } ], "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "
Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.
The impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.
Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.