VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

localstack: vulnerability history, versions and safety

localstack is a package in the PyPI ecosystem. Vulert records 6 vulnerabilities for it across 120 releases, from May 2021 to Nov 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C1 H1 M1 U3
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 localstack vulnerabilities

Vulert verdict on localstack 2026.8.2 i

Updated on 23 Oct 2026

Careful: 2026.8.2 has 3 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2026.8.2 — affected i
  • Vulnerabilities on record 6 over 2 years · 0 in the last year i
  • Latest disclosure 16 Nov 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 3 i
  • Depended on by 12 packages i
  • Stars 65,137 i
  • OpenSSF scorecard 4/10 i
  • Last release this month 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 localstack, 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
2026.8.2 28 Sep 2026 H1 M1 U1 Apache-2.0 No Details →
2026.8.1 10 Sep 2026 H1 M1 U1 Apache-2.0 No Details →
2026.8.0 26 Aug 2026 H1 M1 U1 Apache-2.0 No Details →
2026.7.1 28 Jul 2026 H1 M1 U1 Apache-2.0 No Details →
2026.7.0 22 Jul 2026 H1 M1 U1 Apache-2.0 No Details →
2026.6.1 01 Jul 2026 H1 M1 U1 Apache-2.0 No Details →
2026.6.0 24 Jun 2026 H1 M1 U1 Apache-2.0 No Details →
2026.5.3 10 Jun 2026 H1 M1 U1 Apache-2.0 No Details →
2026.5.1 03 Jun 2026 H1 M1 U1 Apache-2.0 No Details →
2026.5.0 20 May 2026 H1 M1 U1 Apache-2.0 No Details →
2026.4.0 29 Apr 2026 H1 M1 U1 Apache-2.0 No Details →
2026.3.0 23 Mar 2026 H1 M1 U1 Apache-2.0 No Details →
4.14.0 26 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.2.dev116 16 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.2.dev53 12 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.2.dev36 11 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.2.dev3 10 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.2.dev1 02 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.1 02 Feb 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.1.dev1 29 Jan 2026 H1 M1 U1 Apache-2.0 No Details →
4.13.0 29 Jan 2026 H1 M1 U1 Apache-2.0 No Details →
4.12.1.dev159 28 Jan 2026 H1 M1 U1 Apache-2.0 No Details →
4.12.1.dev139 23 Jan 2026 H1 M1 U1 Apache-2.0 No Details →
4.12.1.dev1 11 Dec 2025 H1 M1 U1 Apache-2.0 No Details →
4.12.0 11 Dec 2025 H1 M1 U1 Apache-2.0 No Details →
4.11.2.dev91 11 Dec 2025 H1 M1 U1 Apache-2.0 No Details →
4.11.2.dev51 05 Dec 2025 H1 M1 U1 Apache-2.0 No Details →
4.11.2.dev1 26 Nov 2025 H1 M1 U1 Apache-2.0 No Details →
4.11.1 26 Nov 2025 H1 M1 U1 Apache-2.0 No Details →
4.11.1.dev1 26 Nov 2025 H1 M1 U1 Apache-2.0 No Details →
4.11.0 26 Nov 2025 H1 M1 U1 Apache-2.0 No Details →
4.10.1.dev122 25 Nov 2025 H1 M1 U1 Apache-2.0 No Details →
4.10.1.dev95 21 Nov 2025 H1 M1 U1 Apache-2.0 No Details →
4.10.1.dev1 30 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.10.0 30 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.3.dev131 29 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.3.dev128 29 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.3.dev1 06 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.2 06 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.2.dev1 03 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.1 03 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.1.dev1 02 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.9.0 02 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.2.dev83 02 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.2.dev79 01 Oct 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.2.dev40 24 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.2.dev26 22 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.2.dev1 16 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.1 16 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.1.dev21 16 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.1.dev1 11 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.8.0 11 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.7.1.dev233 10 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.7.1.dev228 10 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.7.1.dev195 03 Sep 2025 H1 M1 U1 Apache-2.0 No Details →
4.7.1.dev123 20 Aug 2025 H1 M1 U1 Apache-2.0 No Details →
4.7.1.dev1 31 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.7.0 31 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.6.1.dev174 30 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.6.1.dev152 28 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.6.1.dev132 25 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.6.1.dev1 03 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.6.0 03 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.5.1.dev140 02 Jul 2025 H1 M1 U1 Apache-2.0 No Details →
4.5.1.dev112 27 Jun 2025 H1 M1 U1 Apache-2.0 No Details →
4.5.1.dev41 13 Jun 2025 H1 M1 U1 Apache-2.0 No Details →
4.5.1.dev1 05 Jun 2025 H1 M1 U1 Apache-2.0 No Details →
4.5.0 05 Jun 2025 H1 M1 U1 Apache-2.0 No Details →
4.4.1.dev123 04 Jun 2025 H1 M1 U1 Apache-2.0 No Details →
4.4.1.dev1 08 May 2025 H1 M1 U1 Apache-2.0 No Details →
4.4.0 08 May 2025 H1 M1 U1 Apache-2.0 No Details →
4.3.1.dev194 07 May 2025 H1 M1 U1 Apache-2.0 No Details →
4.3.1.dev172 05 May 2025 H1 M1 U1 Apache-2.0 No Details →
4.3.1.dev151 30 Apr 2025 H1 M1 U1 Apache-2.0 No Details →
4.3.1.dev58 10 Apr 2025 H1 M1 U1 Apache-2.0 No Details →
4.3.1.dev1 27 Mar 2025 H1 M1 U1 Apache-2.0 No Details →
4.3.0 27 Mar 2025 H1 M1 U1 Apache-2.0 No Details →
4.2.1.dev138 26 Mar 2025 H1 M1 U1 Apache-2.0 No Details →
4.2.1.dev126 25 Mar 2025 H1 M1 U1 Apache-2.0 No Details →
4.2.1.dev1 27 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.2.0 27 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.2.dev104 26 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.2.dev58 19 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.2.dev52 18 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.2.dev1 05 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.1 05 Feb 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.1.dev1 30 Jan 2025 H1 M1 U1 Apache-2.0 No Details →
4.1.0 30 Jan 2025 H1 M1 U1 Apache-2.0 No Details →
4.0.4.dev172 30 Jan 2025 H1 M1 U1 Apache-2.0 No Details →
4.0.4.dev1 29 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.3 29 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.3.dev1 23 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.2 23 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.2.dev1 22 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.1 22 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.1.dev1 21 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
4.0.0 21 Nov 2024 H1 M1 U1 Apache-2.0 No Details →
3.8.1 08 Oct 2024 U1 Apache-2.0 No Details →
3.8.0 03 Oct 2024 U1 Apache-2.0 No Details →
3.7.2 06 Sep 2024 U1 Apache-2.0 No Details →
3.7.1 30 Aug 2024 U1 — No Details →
3.7.0 29 Aug 2024 U1 — No Details →
3.6.0 25 Jul 2024 U1 — No Details →
3.5.0 13 Jun 2024 U1 — No Details →
3.4.0 25 Apr 2024 U1 — No Details →
3.3.0 28 Mar 2024 U1 — No Details →
3.2.0 28 Feb 2024 U1 — No Details →
3.1.0 25 Jan 2024 U1 — No Details →
3.0.2 29 Nov 2023 U1 — No Details →
3.0.1 24 Nov 2023 U1 — No Details →
3.0.0.post4 16 Nov 2023 U1 — No Details →
3.0.0.post3 16 Nov 2023 U1 — No Details →
3.0.0.post2 16 Nov 2023 U1 — No Details →
3.0.0.post1 16 Nov 2023 U1 — No Details →
3.0.0 16 Nov 2023 H1 U1 — No Details →
2.3.2 03 Oct 2023 H1 U1 — No Details →
2.3.1 29 Sep 2023 H1 U1 — No Details →
2.3.0 28 Sep 2023 H1 U1 — No Details →
2.2.0 20 Jul 2023 H1 U1 — No Details →
2.1.0 25 May 2023 H1 U1 — No Details →

The newest 120 of 355 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 4
  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for localstack

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2021-32090: Command injection in LocalStack 9.8 critical 0.12.10 18 Jun 2021
CVE-2023-48054: Missing SSL Certificate Validation in localstack v2.3.2 7.4 high No fix published 16 Nov 2023
CVE-2023-48054: Missing SSL certificate validation in localstack 7.4 high No fix published 16 Nov 2023
Cross-site scripting in LocalStack 6.1 medium No fix published 18 Jun 2021
CVE-2021-32090: Arbitrary Shell Command Injection in StackLift LocalStack N/A unrated 0.12.6.1 07 May 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 localstack

Is localstack safe to use?

Vulert records 6 vulnerabilities for localstack in PyPI: 1 critical, 1 high, 1 medium and 0 low, plus 3 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is localstack's Vulert package health score?

Vulert scores localstack 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of localstack affected?

Yes. 2026.8.2, the version you would install today, has 3 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of localstack should I use?

2026.8.2 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 localstack have?

6 vulnerabilities are recorded for localstack in the PyPI ecosystem: 1 critical, 1 high, 1 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new localstack vulnerabilities disclosed?

0 vulnerabilities were recorded for localstack in the last 12 months, and the oldest entry in this database dates to 07 May 2021. 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 localstack 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 localstack for upcoming vulnerabilities?

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