VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aws-encryption-sdk-cli: vulnerability history, versions and safety

aws-encryption-sdk-cli is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 10 releases, from Oct 2020 to Jun 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aws-encryption-sdk-cli vulnerabilities

Vulert verdict on aws-encryption-sdk-cli 4.3.0 i

Updated on 23 Oct 2026

Good news: 4.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 4.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.3.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 01 Jun 2021 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 10 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for aws-encryption-sdk-cli, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.3.0 27 Nov 2025 none Apache-2.0 — Details →
4.2.0 09 Sep 2024 none Apache-2.0 — Details →
4.1.0 11 Nov 2021 none Apache-2.0 — Details →
4.0.0 13 Jul 2021 none Apache-2.0 — Details →
3.1.0 13 Jul 2021 none Apache-2.0 — Details →
3.0.0 16 Jun 2021 none Apache-2.0 — Details →
2.2.0 27 May 2021 none Apache-2.0 — Details →
1.9.0 27 May 2021 none Apache-2.0 — Details →
2.1.0 27 Oct 2020 none Apache-2.0 — Details →
1.8.0 27 Oct 2020 M1 Apache-2.0 Yes Details →
2.0.0 25 Sep 2020 none Apache-2.0 — Details →
1.7.0 25 Sep 2020 M1 L1 Apache-2.0 Yes Details →
1.1.7 15 Oct 2019 M1 L1 Apache-2.0 Yes Details →
1.1.6 30 Sep 2019 M1 L1 Apache-2.0 Yes Details →
1.1.5 02 Aug 2018 M1 L1 Apache-2.0 Yes Details →
1.1.4 15 Jan 2018 M1 L1 Apache-2.0 Yes Details →
1.1.3 05 Dec 2017 M1 L1 Apache-2.0 Yes Details →
1.1.2 22 Nov 2017 M1 L1 Apache-2.0 Yes Details →
1.1.1 21 Nov 2017 M1 L1 Apache-2.0 Yes Details →
1.1.0 18 Nov 2017 M1 L1 Apache-2.0 Yes Details →

All 20 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for aws-encryption-sdk-cli

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
AWS Encryption CLI does not correctly implement strict mode N/A low 1.8.0 28 Oct 2020
Improper Verification of Cryptographic Signature in aws-encryption-sdk-cli N/A medium 1.9.0 01 Jun 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About aws-encryption-sdk-cli

Is aws-encryption-sdk-cli safe to use?

Vulert records 2 vulnerabilities for aws-encryption-sdk-cli in PyPI: 0 critical, 0 high, 1 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is aws-encryption-sdk-cli's Vulert package health score?

Vulert scores aws-encryption-sdk-cli 82/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of aws-encryption-sdk-cli affected?

No. 4.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of aws-encryption-sdk-cli should I use?

4.3.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does aws-encryption-sdk-cli have?

2 vulnerabilities are recorded for aws-encryption-sdk-cli in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new aws-encryption-sdk-cli vulnerabilities disclosed?

0 vulnerabilities were recorded for aws-encryption-sdk-cli in the last 12 months, and the oldest entry in this database dates to 28 Oct 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of aws-encryption-sdk-cli are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor aws-encryption-sdk-cli for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the aws-encryption-sdk-cli version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.