How severe is GHSA-65p9-r9h6-22vj?

GHSA-65p9-r9h6-22vj has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-65p9-r9h6-22vj?

GHSA-65p9-r9h6-22vj affects the following packages: aws-lc-sys (crates.io), aws-lc-fips-sys (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-65p9-r9h6-22vj?

Update aws-lc-sys to 0.38.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65p9-r9h6-22vj is resolved across your whole dependency graph.

How do I detect GHSA-65p9-r9h6-22vj in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aws-lc-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-65p9-r9h6-22vj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-65p9-r9h6-22vj actively exploited in the wild?

No public exploit code has been indexed for GHSA-65p9-r9h6-22vj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-65p9-r9h6-22vj?

GHSA-65p9-r9h6-22vj has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-65p9-r9h6-22vj?

GHSA-65p9-r9h6-22vj is classified as CWE-208 (CWE-208). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-65p9-r9h6-22vj published, and has it been updated?

GHSA-65p9-r9h6-22vj was published on March 3, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

MEDIUM severity

AWS-LC has Timing Side-Channel in AES-CCM Tag VerificationGHSA-65p9-r9h6-22vj

MEDIUM

GHSA-65p9-r9h6-22vj is a medium-severity (CVSS 5.9) CWE-208 vulnerability in aws-lc-sys. A fix is available for aws-lc-sys — see the affected versions and patch details below.

Also known asCVE-2026-3337 GHSA-frmv-5gcm-jwxhRUSTSEC-2026-0043RUSTSEC-2026-0045

Published

Mar 3, 2026

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-65p9-r9h6-22vj.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🦀aws-lc-sys🦀aws-lc-fips-sys

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Summary

AWS-LC is an open-source, general-purpose cryptographic library.

Impact

Observable 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. 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.

Impacted versions:

aws-lc-sys versions: >= 0.14.0, < 0.38.0
aws-lc-fips-sys versions: >= v0.13.0, < 0.13.12.

Patches

The patch is included in aws-lc-sys v.0.38.0 and aws-lc-fips-sys v0.13.12.

Workarounds

In 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.

Otherwise, 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.

Resources

If there are any questions or comments about this advisory, contact [AWS/Amazon] Security via thevulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.

Acknowledgement

AWS-LC would like to thank Joshua Rogers (https://joshua.hu/) for collaborating on this issue through the coordinated vulnerability disclosure process.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`aws-lc-sys`	≥ 0.14.0&&< 0.38.0	0.38.0`cargo update -p aws-lc-sys --precise 0.38.0`
🦀crates.io	`aws-lc-fips-sys`	≥ 0.13.0&&< 0.13.12	0.13.12`cargo update -p aws-lc-fips-sys --precise 0.13.12`

Affected Products

3 products · 4 configurations

Application

aws libcryptoamazon

≥ 3.0.0 && < 3.2.0

range

Application

aws-lc-fips-sysamazon

≥ 0.13.0 && < 0.13.12

range

Application

aws-lc-sysamazon

≥ 0.14.0 && < 0.38.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aws-lc-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aws-lc-sys to 0.38.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-65p9-r9h6-22vj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-65p9-r9h6-22vj (CC BY 4.0)

Frequently Asked Questions

### Summary AWS-LC is an open-source, general-purpose cryptographic library. ### Impact Observable 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. 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