Aws Lc Fips SysApplication · Amazon
CVE-2026-3337
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedObservable 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceObservable timing discrepancy in AES-CCM decryption in AWS-LC allows an unauthenticated attacker to determine authentication tag validity via timing side-channel analysis. The vulnerability affects EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm cipher implementations through the EVP CIPHER API.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Aws Lc Fips SysApplication
>= 0.13.0, < 0.13.12
Aws Lc SysApplication
>= 0.14.0, < 0.38.0>= 1.21.0, < 1.69.0>= 3.0.0, < 3.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify AWS-LC library versionLocate the AWS-LC library binary or inspect linked libraries via 'ldd' on Linux or dependency list on other platforms. Check version string in library file name, or run 'strings libaws-lc.so* | grep -i "aws-lc" | head -5' to find version metadataAffected if version is >= 0.13.0 and < 0.13.12 (FIPS), or >= 0.14.0 and < 0.38.0 (standard), or >= 1.21.0 and < 1.69.0, or >= 3.0.0 and < 3.2.0 (libcrypto)
-
Confirm AES-CCM cipher usageSearch application source code or configuration for EVP_aes_128_ccm, EVP_aes_192_ccm, or EVP_aes_256_ccm function calls, or inspect cipher suite configuration files for CCM-based suitesAffected if any of these EVP_AES_CCM cipher functions are called in the code or enabled in configuration
-
Verify decryption operationsReview code paths that perform decryption using the identified AES-CCM ciphers. Look for EVP_DecryptInit, EVP_DecryptUpdate, or EVP_DecryptFinal calls in combination with CCM modeAffected if the application performs decryption operations with AES-CCM, not just encryption
-
Check if running AWS managed serviceDetermine if the application runs on AWS infrastructure (Lambda, EC2, ECS, EKS, etc.) or uses AWS SDK with managed cryptographic operationsAffected if application is self-hosted or uses AWS-LC directly rather than AWS-managed cryptographic services
You are affected if your environment uses a vulnerable AWS-LC version AND performs AES-CCM decryption operations; applications relying solely on AWS managed services are not affected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.13.120.38.01.69.0
Upgrade AWS-LC library to version 1.69.0 or later. Applications using AWS managed services do not require action as AWS handles the underlying cryptographic library.
aws-libcrypto: 1.69.0 or 3.2.0; aws-lc-sys: 38.0; aws-lc-fips-sys: 0.13.12
- Identify the AWS-LC library used by your application (aws-libcrypto, aws-lc-sys, or aws-lc-fips-sys)
- For Rust projects using aws-lc-sys or aws-lc-fips-sys: Run 'cargo update aws-lc-sys' or 'cargo update aws-lc-fips-sys' to update to the latest compatible version
- For C/C++ projects: Update the dependency version in your build configuration (CMake, Makefile, or package manager)
- If using a package manager (Homebrew, apt, yum): Run 'brew upgrade aws-lc' or equivalent to fetch the fixed version
- Rebuild and redeploy your application to include the updated library
- Verify the installed AWS-LC version matches the fixed release (1.69.0 or 3.2.0 for aws-libcrypto, 38.0 for aws-lc-sys, 0.13.12 for aws-lc-fips-sys)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Aws Lc Fips Sys
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3337 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data