CVE-2026-6550: AWS Encryption SDK for Python Key Commitment Policy Bypass Vulnerability
MODERATECVE-2026-6550 is a MODERATE (CVSS 4.7) key commitment policy bypass vulnerability (CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')) affecting AWS Encryption SDK for Python libraries in the PyPI ecosystem. The issue involves key commitment policy bypass via shared key cache. Remediation is available by upgrading affected packages to version 3.3.1, 4.0.5.
CVE-2026-6550 at a Glance
Security Impact
CVSS: 4.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-6550
To remediate this vulnerability, upgrade all affected AWS Encryption SDK for Python dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install aws-encryption-sdk>=3.3.1
pip install aws-encryption-sdk>=4.0.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show aws-encryption-sdk
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-6550, inspect your installed packages using pip:
pip show aws-encryption-sdk
Analyze the terminal output to locate any version of AWS Encryption SDK for Python in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3.1), your application is affected.
Note: The pip show aws-encryption-sdk command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade'), where a protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties. In AWS Encryption SDK for Python, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-6550 Affected AWS Encryption SDK for Python Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
aws-encryption-sdk
|
PyPI |
≥ 2.0.0
< 3.3.1
|
3.3.1
|
|
aws-encryption-sdk
|
PyPI |
≥ 4.0.0
< 4.0.5
|
4.0.5
|
References
Frequently Asked Questions
What is CVE-2026-6550?
Which AWS Encryption SDK for Python versions are affected?
What version fixes CVE-2026-6550?
Is aws-encryption-sdk affected?
What is the CVSS score of CVE-2026-6550?
What CWE is associated with CVE-2026-6550?
How can I check PyPI dependencies for CVE-2026-6550?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-v638-38fc-rhfv",
"modified" : "2026-04-24T15:59:17Z",
"published" : "2026-04-24T15:59:17Z",
"aliases" : [ "CVE-2026-6550" ],
"summary" : "AWS Encryption SDK for Python: Key commitment policy bypass via shared key cache",
"details" : "## Summary\nAWS Encryption SDK (ESDK) for Python is a client-side encryption library. An issue exists where, under certain circumstances, a specific cryptographic algorithm downgrade in the caching layer 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.\n\n## Impact\nThis issue requires all of the following conditions to be true: (1) Two ESDK for Python clients with different commitment policies share a single CachingCryptoMaterialsManager instance within the same process. (2) The client with the weaker commitment policy encrypts first, warming the cache. (3) Both clients use matching encryption contexts. (4) Both clients use the pre-configured default algorithm suite.\n\nThese conditions may occur during a migration from ESDK for Python v1 to newer versions, as v1 did not support key commitment.\n\nWhen the weaker-policy client encrypts first, the cache stores encryption materials that do not enforce key commitment. Subsequent callers — including those configured to require key commitment — are served these cached materials instead of generating new ones that satisfy their policy. This results in encryption without key commitment, meaning the same ciphertext can be validly decrypted to different plaintexts under different keys (the \"Invisible Salamanders\" issue; see https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf). A threat actor who controls ciphertext can cause a recipient to decrypt a message different from what the sender encrypted, breaking message integrity.\n\n## Impacted versions\n- From 2.0 to 2.5.1\n- From 3.0 to 3.3.0\n- From 4.0 to 4.0.4\n\n## Patches\nThis issue has been addressed in ESDK for Python versions 3.3.1 and 4.0.5. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.\n\n## Workarounds\nIf a customer requires operating multiple instances of the Python ESDK each with differently configured key commitment policies, they must not share a key cache.\n\nReferences\nIf there are any questions or comments about this advisory, contact AWS Security through the [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.\n\n## Acknowledgement\nThanks to [1seal.org](http://1seal.org/) for collaborating on this issue through the coordinated vulnerability disclosure process.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N"
}, {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "aws-encryption-sdk"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.0.0"
}, {
"fixed" : "3.3.1"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "< 3.3.0"
}
}, {
"package" : {
"ecosystem" : "PyPI",
"name" : "aws-encryption-sdk"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.0.5"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "< 4.0.4"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv"
}, {
"type" : "WEB",
"url" : "https://github.com/google/security-research/security/advisories/GHSA-wqgp-vphw-hphf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-6550"
}, {
"type" : "WEB",
"url" : "https://aws.amazon.com/security/security-bulletins/2026-017-aws"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/aws/aws-encryption-sdk-python"
}, {
"type" : "WEB",
"url" : "https://github.com/aws/aws-encryption-sdk-python/releases/tag/v3.3.1"
}, {
"type" : "WEB",
"url" : "https://github.com/aws/aws-encryption-sdk-python/releases/tag/v4.0.5"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-757" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-24T15:59:17Z",
"nvd_published_at" : "2026-04-20T20:16:49Z"
}
}