AWS-LC Flaw Exposes Amazon Users to Attacks by Bypassing Certificate Chain Validation
Amazon has released a security bulletin (2026-005-AWS) addressing three high-severity vulnerabilities in its AWS-LC cryptographic library. These vulnerabilities were identified through a coordinated disclosure with the AISLE Research Team and pose…
Amazon has released a security bulletin (2026-005-AWS) addressing three high-severity vulnerabilities in its AWS-LC cryptographic library. These vulnerabilities were identified through a coordinated disclosure with the AISLE Research Team and pose significant risks to cloud infrastructure.
Three distinct issues have been identified in the handling of cryptographic processes by AWS-LC:
CVE-2026-3336: This vulnerability involves a certificate chain validation bypass in the PKCS7_verify() function, allowing unauthenticated users to bypass verification for all but the final signer in PKCS7 objects with multiple signers. CVE-2026-3337: This flaw introduces a timing side-channel during AES-CCM decryption, potentially allowing attackers to determine the validity of an authentication tag. CVE-2026-3338: Similar to CVE-2026-3336, this vulnerability allows unauthenticated users to bypass signature verification for PKCS7 objects containing Authenticated Attributes.
Amazon advises all customers to upgrade to the latest versions of AWS-LC to address these vulnerabilities. The affected versions are:
Amazon has released a security bulletin (2026-005-AWS) addressing three high-severity vulnerabilities in its AWS-LC cryptographic library.
PKCS7 flaws: AWS-LC versions between v1.41.0 and v1.69.0, and aws-lc-sys versions between v0.24.0 and v0.38.0. Timing side-channel flaw: AWS-LC starting from v1.21.0, including AWS-LC-FIPS versions 3.0.0 through 3.2.0.
The vulnerabilities have been addressed in AWS-LC v1.69.0 and aws-lc-sys v0.38.0 for the PKCS7 bypasses, and in AWS-LC v1.69.0, AWS-LC-FIPS-3.2.0, aws-lc-sys v0.38.0, and aws-lc-sys-fips v0.13.12 for the timing side-channel flaw.
Immediate patching is necessary as no known workarounds exist for the certificate and signature validation bypasses. For the timing side-channel vulnerability, temporary mitigation is possible by using specific AES-CCM parameters and routing encryption through the EVP AEAD API with configurations like EVP_aead_aes_128_ccm_bluetooth or EVP_aead_aes_128_ccm_matter .
Based on reporting by GBHackers.
