CVE-2026-6550PYSEC-2026-2387GHSA-V638-38FC-RHFV
Key commitment policy bypass via shared key cache in AWS Encryption SDK for Python
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3.1, 4.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Cryptographic algorithm downgrade in the caching layer of Amazon AWS Encryption SDK for Python before version 3.3.1 and before version 4.0.5 might allow an authenticated local threat actor to bypass key commitment policy enforcement via a shared key cache, resulting in ciphertext that can be decrypted to multiple different plaintexts. To remediate this issue, users should upgrade to version 3.3.1, 4.0.5 or above.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- AWS AWS Encryption SDK for Python
From 2 · through 2.5.1; From 3 · through 3.3.0; From 4 · through 4.0.4
- aws-encryption-sdkPyPI
From 2.0.0 · fixed in 3.3.1; From 4.0.0 · fixed in 4.0.5
- aws-encryption-sdkPyPI
From 2.0.0 · fixed in 3.3.1
- aws-encryption-sdkPyPI
From 4.0.0 · fixed in 4.0.5