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

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). 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
    cargo update -p aws-lc-fips-sys
  • aws-lc-sys (crates.io): upgrade to 0.38.0 or later
    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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.