{"id":"CVE-2026-3337","aliases":["EUVD-2026-9265","GHSA-65p9-r9h6-22vj","GHSA-frmv-5gcm-jwxh","RUSTSEC-2026-0043","RUSTSEC-2026-0045"],"status":"published","title":"Timing Side-Channel in AES-CCM Tag Verification in AWS-LC","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\n\n\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\n\n\n\nCustomers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.","severity":{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.01075,"percentile":0.652,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-208"],"published":"2026-03-02T12:00:00Z","modified":"2026-11-09T11:00:03Z","fixes":[{"ecosystem":"crates.io","package":"aws-lc-sys","fixed_in":["0.38.0"],"sources":["ghsa","osv"]},{"ecosystem":"crates.io","package":"aws-lc-fips-sys","fixed_in":["0.13.12"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"aws-lc-sys","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.14.0"},{"fixed":"0.38.0"}]}]},{"source":"ghsa","ecosystem":"crates.io","package":"aws-lc-fips-sys","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.13.0"},{"fixed":"0.13.12"}]}]},{"source":"osv","ecosystem":"crates.io","package":"aws-lc-sys","ranges":[{"type":"SEMVER","events":[{"introduced":"0.14.0"},{"fixed":"0.38.0"}]}]},{"source":"osv","ecosystem":"crates.io","package":"aws-lc-fips-sys","ranges":[{"type":"SEMVER","events":[{"introduced":"0.13.0"},{"fixed":"0.13.12"}]}]},{"source":"osv","ecosystem":"crates.io","package":"aws-lc-fips-sys","ranges":[{"type":"SEMVER","events":[{"introduced":"0.13.0"},{"fixed":"0.13.12"}]}]},{"source":"osv","ecosystem":"crates.io","package":"aws-lc-sys","ranges":[{"type":"SEMVER","events":[{"introduced":"0.14.0"},{"fixed":"0.38.0"}]}]}],"products":[{"vendor":"amazon","product":"aws-lc-fips-sys"},{"vendor":"amazon","product":"aws-lc-sys"},{"vendor":"amazon","product":"aws_libcrypto"},{"vendor":"aws","product":"aws-lc"},{"vendor":"aws","product":"aws-lc-fips"}],"references":[{"url":"https://aws.amazon.com/security/security-bulletins/2026-005-AWS/","tags":["vendor-advisory","Vendor Advisory","advisory"]},{"url":"https://github.com/aws/aws-lc/releases/tag/v1.69.0","tags":["patch","Release Notes","fix"]},{"url":"https://github.com/aws/aws-lc/security/advisories/GHSA-frmv-5gcm-jwxh","tags":["third-party-advisory","Vendor Advisory","advisory","web"]},{"url":"https://github.com/aws/aws-lc-rs/security/advisories/GHSA-65p9-r9h6-22vj","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-3337","tags":["advisory"]},{"url":"https://aws.amazon.com/security/security-bulletins/2026-005-AWS","tags":["web"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2026-0043.html","tags":["web","advisory"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2026-0045.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-65p9-r9h6-22vj"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/3xxx/CVE-2026-3337.json","tags":["advisory"]},{"url":"https://github.com/aws/aws-lc-rs","tags":["package"]},{"url":"https://crates.io/crates/aws-lc-fips-sys","tags":["package"]},{"url":"https://crates.io/crates/aws-lc-sys","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-3337","title":"Timing Side-Channel in AES-CCM Tag Verification in AWS-LC","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\n\n\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\n\n\n\nCustomers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.","status":"published","published":"2026-03-02T21:20:08.532Z","modified":"2026-03-03T20:04:27.577Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high","assessor":"cna"},{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-208"],"updated_at":"2026-11-02T13:48:58.05327Z"}],"euvd":[{"id":"EUVD-2026-9265","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\n\n\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\n\n\n\nCustomers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.","status":"published","published":"2026-03-02T21:20:08Z","modified":"2026-03-03T20:04:27Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T19:48:11.637968Z"}],"ghsa":[{"id":"GHSA-65p9-r9h6-22vj","title":"AWS-LC has Timing Side-Channel in AES-CCM Tag Verification","description":"### Summary\nAWS-LC is an open-source, general-purpose cryptographic library.\n\n### Impact\nObservable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\nCustomers of AWS services do not need to take action. aws-lc-sys and aws-lc-fips-sys contain code from AWS-LC. Applications using aws-lc-sys or aws-lc-fips-sys should upgrade to the most recent releases of aws-lc-sys or aws-lc-fips-sys.\n\n### Impacted versions: \n - aws-lc-sys versions: \u003e= 0.14.0, \u003c 0.38.0\n - aws-lc-fips-sys versions: \u003e= v0.13.0, \u003c 0.13.12.\n\n### Patches\nThe patch is included in aws-lc-sys v.0.38.0 and aws-lc-fips-sys v0.13.12.\n\n### Workarounds\nIn the special cases of using AES-CCM with (M=4, L=2), (M=8, L=2), or (M=16, L=2), applications can workaround this issue by using AES-CCM through the EVP AEAD API using implementations EVP_aead_aes_128_ccm_bluetooth, EVP_aead_aes_128_ccm_bluetooth_8, and, EVP_aead_aes_128_ccm_matter respectively.\n\nOtherwise, there is no workaround and applications using aws-lc-sys or aws-lc-fips-sys should upgrade to the most recent releases of aws-lc-sys or aws-lc-fips-sys.\n\n### Resources\nIf there are any questions or comments about this advisory, contact [AWS/Amazon] Security via the[vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.\n\n### Acknowledgement\nAWS-LC would like to thank Joshua Rogers (https://joshua.hu/) for collaborating on this issue through the coordinated vulnerability disclosure process.","status":"published","published":"2026-03-03T20:09:25Z","modified":"2026-03-20T21:31:34Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"},{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-208"],"updated_at":"2026-11-02T14:39:40.633038Z"}],"nvd":[{"id":"CVE-2026-3337","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\n\n\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\n\n\n\nCustomers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.","status":"published","published":"2026-03-02T22:16:32.093Z","modified":"2026-06-17T10:43:25.807Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/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","level":"high","assessor":"secondary"},{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-208"],"updated_at":"2026-11-02T14:12:07.420927Z"}],"osv":[{"id":"CVE-2026-3337","title":"Timing Side-Channel in AES-CCM Tag Verification in AWS-LC","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\n\n\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\n\n\n\nCustomers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.","status":"published","published":"2026-03-02T21:20:08.532Z","modified":"2026-10-28T11:11:52.095477207Z","cvss":[{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-208"],"updated_at":"2026-11-02T15:45:01.896044Z"},{"id":"GHSA-65p9-r9h6-22vj","title":"AWS-LC has Timing Side-Channel in AES-CCM Tag Verification","description":"### Summary\nAWS-LC is an open-source, general-purpose cryptographic library.\n\n### Impact\nObservable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated user to potentially determine authentication tag validity via timing analysis.\n\nThe impacted implementations are through the EVP CIPHER API: EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm.\n\nCustomers of AWS services do not need to take action. aws-lc-sys and aws-lc-fips-sys contain code from AWS-LC. Applications using aws-lc-sys or aws-lc-fips-sys should upgrade to the most recent releases of aws-lc-sys or aws-lc-fips-sys.\n\n### Impacted versions: \n - aws-lc-sys versions: \u003e= 0.14.0, \u003c 0.38.0\n - aws-lc-fips-sys versions: \u003e= v0.13.0, \u003c 0.13.12.\n\n### Patches\nThe patch is included in aws-lc-sys v.0.38.0 and aws-lc-fips-sys v0.13.12.\n\n### Workarounds\nIn the special cases of using AES-CCM with (M=4, L=2), (M=8, L=2), or (M=16, L=2), applications can workaround this issue by using AES-CCM through the EVP AEAD API using implementations EVP_aead_aes_128_ccm_bluetooth, EVP_aead_aes_128_ccm_bluetooth_8, and, EVP_aead_aes_128_ccm_matter respectively.\n\nOtherwise, there is no workaround and applications using aws-lc-sys or aws-lc-fips-sys should upgrade to the most recent releases of aws-lc-sys or aws-lc-fips-sys.\n\n### Resources\nIf there are any questions or comments about this advisory, contact [AWS/Amazon] Security via the[vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.\n\n### Acknowledgement\nAWS-LC would like to thank Joshua Rogers (https://joshua.hu/) for collaborating on this issue through the coordinated vulnerability disclosure process.","status":"published","published":"2026-03-03T20:09:25Z","modified":"2026-09-10T03:50:37.687975213Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"},{"version":"4.0","score":8.2,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-208"],"updated_at":"2026-11-02T15:46:39.266402Z"},{"id":"RUSTSEC-2026-0043","title":"Timing Side-Channel in AES-CCM Tag Verification in AWS-LC","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an\nunauthenticated user to potentially determine authentication tag validity\nvia timing analysis.\n\nThe impacted implementations are through the EVP CIPHER API:\n`EVP_aes_128_ccm`, `EVP_aes_192_ccm`, and `EVP_aes_256_ccm`.\n\nCustomers of AWS services do not need to take action. `aws-lc-fips-sys`\ncontains code from AWS-LC. Applications using `aws-lc-fips-sys` should\nupgrade to the most recent release of `aws-lc-fips-sys`.\n\n## Workarounds\n\nIn the special cases of using AES-CCM with (M=4, L=2), (M=8, L=2), or\n(M=16, L=2), applications can workaround this issue by using AES-CCM\nthrough the EVP AEAD API using implementations\n`EVP_aead_aes_128_ccm_bluetooth`, `EVP_aead_aes_128_ccm_bluetooth_8`,\nand `EVP_aead_aes_128_ccm_matter` respectively.\n\nOtherwise, there is no workaround and applications using `aws-lc-fips-sys`\nshould upgrade to the most recent release of `aws-lc-fips-sys`.","status":"published","published":"2026-03-02T12:00:00Z","modified":"2026-11-09T11:00:03.732800176Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-09T11:24:16.480676Z"},{"id":"RUSTSEC-2026-0045","title":"Timing Side-Channel in AES-CCM Tag Verification in AWS-LC","description":"Observable timing discrepancy in AES-CCM decryption in AWS-LC allows an\nunauthenticated user to potentially determine authentication tag validity\nvia timing analysis.\n\nThe impacted implementations are through the EVP CIPHER API:\n`EVP_aes_128_ccm`, `EVP_aes_192_ccm`, and `EVP_aes_256_ccm`.\n\nCustomers of AWS services do not need to take action. `aws-lc-sys` contains\ncode from AWS-LC. Applications using `aws-lc-sys` should upgrade to the most\nrecent release of `aws-lc-sys`.\n\n## Workarounds\n\nIn the special cases of using AES-CCM with (M=4, L=2), (M=8, L=2), or\n(M=16, L=2), applications can workaround this issue by using AES-CCM through\nthe EVP AEAD API using implementations `EVP_aead_aes_128_ccm_bluetooth`,\n`EVP_aead_aes_128_ccm_bluetooth_8`, and `EVP_aead_aes_128_ccm_matter`\nrespectively.\n\nOtherwise, there is no workaround and applications using `aws-lc-sys` should\nupgrade to the most recent release.","status":"published","published":"2026-03-02T12:00:00Z","modified":"2026-11-09T11:00:03.736773978Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"medium"}],"updated_at":"2026-11-09T11:24:16.480676Z"}]}}
