# CVE-2026-3337: RUSTSEC-2026-0043 - Timing Side-Channel in AES-CCM Tag Verification in AWS-LC

Source: https://junglewise.ai/threats/cve-2026-3337-aws-lc-has-timing-side-channel-in-aes-ccm-tag-verification  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-03-02  
License: CC BY 4.0 with a link back

CVE-2026-3337 · Severity: low · CVSS 3.1 · Published 2026-03-02

Timing Side-Channel in AES-CCM Tag Verification in AWS-LC

Technologies: [aws-lc-sys (crates.io)](https://junglewise.ai/threats/technologies/crates-io-aws-lc-sys). Vendors: [crates.io](https://junglewise.ai/threats/vendors/crates-io).

## Quick answers

**Is CVE-2026-3337 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-3337 being exploited in the wild.

**How severe is CVE-2026-3337?** Low severity, with a CVSS score of 3.1, published 2 March 2026.

**Which products and versions are affected?** aws-lc-fips-sys (crates.io) SEMVER:introduced=0.13.0,fixed=0.13.12; aws-lc-sys (crates.io) SEMVER:introduced=0.14.0,fixed=0.38.0.

**Is there a fix for CVE-2026-3337?** Yes. aws-lc-fips-sys (crates.io): upgrade to 0.13.12 or later; aws-lc-sys (crates.io): upgrade to 0.38.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-3337?** Check whether you run aws-lc-fips-sys (crates.io) or aws-lc-sys (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- aws-lc-fips-sys (crates.io): upgrade to 0.13.12 or later

  ```sh
  cargo update -p aws-lc-fips-sys
  ```

- aws-lc-sys (crates.io): upgrade to 0.38.0 or later

  ```sh
  cargo update -p aws-lc-sys
  ```


## Affected products

- aws-lc-fips-sys (crates.io) SEMVER:introduced=0.13.0,fixed=0.13.12
- aws-lc-sys (crates.io) SEMVER:introduced=0.14.0,fixed=0.38.0

## Identifiers

- CVE-2026-3337
- GHSA-65p9-r9h6-22vj
- RUSTSEC-2026-0043
- RUSTSEC-2026-0045

## Related threats

- [AWS-LC X.509 Name Constraints Bypass via Wildcard/Unicode CN](https://junglewise.ai/threats/aws-lc-x-509-name-constraints-bypass-via-wildcard-unicode-cn-3aa77348)
- [RUSTSEC-2026-0044 - AWS-LC X.509 Name Constraints Bypass via Wildcard/Unicode CN](https://junglewise.ai/threats/rustsec-2026-0044-aws-lc-x-509-name-constraints-bypass-via-wildcard-64993ed0)
- [RUSTSEC-2026-0048 - CRL Distribution Point Scope Check Logic Error in AWS-LC](https://junglewise.ai/threats/cve-2026-4428-aws-aws-lc-revocation-check-bypass-in-x-509-certificate)
- [AWS AWS-LC signature verification bypass in PKCS7_verify](https://junglewise.ai/threats/cve-2026-3338-aws-aws-lc-signature-verification-bypass-in-pkcs7-verify)
- [AWS AWS-LC certificate chain validation bypass in PKCS7_verify](https://junglewise.ai/threats/cve-2026-3336-aws-aws-lc-certificate-chain-validation-bypass-in-pkcs7-verify)