What is GHSA-2XWP-M7MQ-7Q3R?

GHSA-2XWP-M7MQ-7Q3R is a low-severity security vulnerability in aws-encryption-sdk-cli (pip), affecting versions < 1.8.0. It is fixed in 1.8.0, 2.1.0.

Which versions of aws-encryption-sdk-cli are affected by GHSA-2XWP-M7MQ-7Q3R?

aws-encryption-sdk-cli (pip) versions < 1.8.0 is affected.

Is there a fix for GHSA-2XWP-M7MQ-7Q3R?

Yes. GHSA-2XWP-M7MQ-7Q3R is fixed in 1.8.0, 2.1.0. Upgrade to this version or later.

Is GHSA-2XWP-M7MQ-7Q3R exploitable, and should I be worried?

Whether GHSA-2XWP-M7MQ-7Q3R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-2XWP-M7MQ-7Q3R is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-2XWP-M7MQ-7Q3R in aws-encryption-sdk-cli

Q: Which versions of aws-encryption-sdk-cli are affected by GHSA-2XWP-M7MQ-7Q3R?

aws-encryption-sdk-cli (pip) versions < 1.8.0 is affected.

Q: Is there a fix for GHSA-2XWP-M7MQ-7Q3R?

Yes. GHSA-2XWP-M7MQ-7Q3R is fixed in 1.8.0, 2.1.0. Upgrade to this version or later.

Q: Is GHSA-2XWP-M7MQ-7Q3R exploitable, and should I be worried?

Whether GHSA-2XWP-M7MQ-7Q3R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-2XWP-M7MQ-7Q3R is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-2XWP-M7MQ-7Q3R?

Upgrade: aws-encryption-sdk-cli to 1.8.0 or later, aws-encryption-sdk-cli to 2.1.0 or later.

Summary

CLI does not correctly implement strict mode

In the affected versions, the AWS Encryption CLI operated in "discovery mode" even when "strict mode" was specified. Although decryption only succeeded if the user had permission to decrypt with at least one of the CMKs, decryption could be successful using a CMK that was not included in the user-defined set when the CLI was operating in "strict mode."

Affected users should upgrade to Encryption CLI v1.8.x or v2.1.x as soon as possible.

Impact

Affected versions

aws-encryption-sdk-cli (< 1.8.0) aws-encryption-sdk-cli (>= 2.0.0, < 2.1.0)

Security releases

aws-encryption-sdk-cli → 1.8.0 (pip) aws-encryption-sdk-cli → 2.1.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

aws-encryption-sdk-cli to 1.8.0 or later; aws-encryption-sdk-cli to 2.1.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-2XWP-M7MQ-7Q3R? GHSA-2XWP-M7MQ-7Q3R is a low-severity security vulnerability in aws-encryption-sdk-cli (pip), affecting versions < 1.8.0. It is fixed in 1.8.0, 2.1.0.
Which versions of aws-encryption-sdk-cli are affected by GHSA-2XWP-M7MQ-7Q3R? aws-encryption-sdk-cli (pip) versions < 1.8.0 is affected.
Is there a fix for GHSA-2XWP-M7MQ-7Q3R? Yes. GHSA-2XWP-M7MQ-7Q3R is fixed in 1.8.0, 2.1.0. Upgrade to this version or later.
Is GHSA-2XWP-M7MQ-7Q3R exploitable, and should I be worried? Whether GHSA-2XWP-M7MQ-7Q3R is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-2XWP-M7MQ-7Q3R is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-2XWP-M7MQ-7Q3R?
- Upgrade aws-encryption-sdk-cli to 1.8.0 or later
- Upgrade aws-encryption-sdk-cli to 2.1.0 or later

Other vulnerabilities in aws-encryption-sdk-cli

CVE-IDSeverityPackage summary

GHSA-89V2-G37M-G3FFMediumaws-encryption-sdk-cli: Improper Verification of Cryptographic Signature in aws-encryption-sdk-cli