VulnerabilityPublished 2 Mar 2026Updated 9 Nov 2026

CVE-2026-3337: Aws lc sys · Timing Side-Channel in AES-CCM Tag Verification in AWS-LC

Affects aws-lc-sysSource GCVE Database

Compare

Authoritative record:CVE-2026-3337· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.38.0 when convenient.

Data as of 9 Nov 2026, 11:23 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.38.0

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade aws-lc-sys to 0.38.0.

Affected software

Product	Affected	Fixed in
crates.ioaws-lc-sys`pkg:cargo/aws-lc-sys`Other threats	Affected >=0.14.0 <0.38.0	Fixed in 0.38.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in aws-lc-sys version 0.38.0 and later; users should upgrade to this version to remediate the vulnerability. AWS customers using AWS cloud services do not need to take any action as the vendor manages remediation for these services. For applications using AES-CCM with parameters (M=4, L=2), (M=8, L=2), or (M=16, L=2), a workaround is to use the EVP AEAD API implementations EVP_aead_aes_128_ccm_bluetooth, EVP_aead_aes_128_ccm_bluetooth_8, or EVP_aead_aes_128_ccm_matter respectively. No other workarounds are available.

Description

A timing side-channel vulnerability exists in the AES-CCM tag verification implementation in aws-lc-sys versions from 0.14.0 up to but not including 0.38.0. This flaw allows an unauthenticated attacker to potentially determine the validity of authentication tags by measuring timing discrepancies during decryption. The issue affects the EVP CIPHER API implementations EVP_aes_128_ccm, EVP_aes_192_ccm, and EVP_aes_256_ccm. AWS customers using AWS services are not required to take action, but applications using aws-lc-sys should upgrade to version 0.38.0 or later. Workarounds exist only for specific AES-CCM parameter sets by using the EVP AEAD API with certain implementations; otherwise, upgrading is necessary.

Impact

The vulnerability allows an unauthenticated attacker to perform timing analysis during AES-CCM tag verification, potentially revealing whether an authentication tag is valid. This compromises the integrity assurance of encrypted messages but does not affect confidentiality or availability. The CVSS v3.1 score is 5.9 (medium severity), reflecting the network attack vector, high attack complexity, no privileges required, no user interaction, and impact limited to integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 11:22 UTC

Technical details

References

Community reviews

Related threats