cve.bz

CVE-2026-6550 aws aws encryption sdk for python: Algorithm Downgrade

5.7 mediumEPSS 0.10%Fix available

Medium (5.7) in aws aws encryption sdk for python. EPSS 0.10% estimated probability of exploitation activity in the next 30 days. Fixed in aws-encryption-sdk 3.3.1, 4.0.5.

On this page
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.

Severity

CVSS 4.0

5.7 medium
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
0.10% (unchanged from 0.10% a week ago; 0.10% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-757 Selection of Less-Secure Algorithm During Negotiation (Algorithm Downgrade)
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • aws-encryption-sdk (PyPI): fixed in 3.3.1, 4.0.5

Ask an AI about this CVE

Show the promptExplain CVE-2026-6550 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6550?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6550?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6550 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • aws:aws encryption sdk for python

Versions

From the CNA's record in the CVE List.

ProductAffected
AWS Encryption SDK for Pythonfrom 2 through 2.5.1
AWS Encryption SDK for Pythonfrom 3 through 3.3.0
AWS Encryption SDK for Pythonfrom 4 through 4.0.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v638-38fc-rhfvPyPIaws-encryption-sdk>=2.0.0 <3.3.13.3.1
GHSA-v638-38fc-rhfvPyPIaws-encryption-sdk>=4.0.0 <4.0.54.0.5
PYSEC-2026-2387PyPIaws-encryption-sdk>=2.0.0 <3.3.1
>=4.0.0 <4.0.5
3.3.1, 4.0.5

Attack patterns (CAPEC)

  • CAPEC-220 Client-Server Protocol Manipulation Severity: Medium
  • CAPEC-606 Weakening of Cellular Encryption Severity: High
  • CAPEC-620 Drop Encryption Level Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON