Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially…
Historical advisory recorded 25 Oct 2026 08:17:18 UTC. Read the latest advisory.
nvd · CVE-2026-3337
PublishedObservable 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.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-3337
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-208
Original publisher date fields
published: 2026-03-02T22:16:32.093
lastModified: 2026-06-17T10:43:25.807
4 source CPE criteria · context only
- cpe:2.3:a:amazon:aws-lc-fips-sys:*:*:*:*:*:rust:*:*
- cpe:2.3:a:amazon:aws-lc-sys:*:*:*:*:*:rust:*:*
- cpe:2.3:a:amazon:aws_libcrypto:*:*:*:*:*:*:*:*
- cpe:2.3:a:amazon:aws_libcrypto:*:*:*:*:fips:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON