VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

galaxy-importer: vulnerability history, versions and safety

galaxy-importer is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 104 releases, from Nov 2023 to Jul 2026. 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 U1
i
2 with no fix published

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

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all galaxy-importer vulnerabilities

Vulert verdict on galaxy-importer 0.5.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

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 0.5.0 — affected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 6.3 i
  • With no published fix 2 i
  • Depended on by 1 packages i
  • Stars 28 i
  • OpenSSF scorecard 6/10 i
  • Last release 42 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 galaxy-importer, 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
0.4.44 13 Oct 2026 M1 U1 Apache-2.0 No Details →
0.4.43 21 Aug 2026 M1 U1 Apache-2.0 No Details →
0.4.42 13 Aug 2026 M1 U1 Apache-2.0 No Details →
0.4.41 04 Aug 2026 M1 U1 Apache-2.0 No Details →
0.4.40 02 Jul 2026 M1 U1 Apache-2.0 No Details →
0.4.39 06 May 2026 M1 U1 Apache-2.0 No Details →
0.4.38 09 Apr 2026 M1 U1 Apache-2.0 No Details →
0.4.37 12 Jan 2026 M1 U1 Apache-2.0 No Details →
0.4.36 02 Dec 2025 M1 U1 Apache-2.0 No Details →
0.4.35 25 Nov 2025 M1 U1 Apache-2.0 No Details →
0.4.34 07 Oct 2025 M1 U1 Apache-2.0 No Details →
0.4.33 27 Aug 2025 M1 U1 Apache-2.0 No Details →
0.4.32 21 Aug 2025 M1 U1 Apache-2.0 No Details →
0.4.31 13 Jun 2025 M1 U1 Apache-2.0 No Details →
0.4.30 28 May 2025 M1 U1 Apache-2.0 No Details →
0.4.29 10 Mar 2025 M1 U1 Apache-2.0 No Details →
0.4.28 11 Feb 2025 M1 U1 Apache-2.0 No Details →
0.4.27 16 Dec 2024 M1 U1 Apache-2.0 No Details →
0.4.26 23 Oct 2024 M1 U1 Apache-2.0 No Details →
0.4.25 18 Sep 2024 M1 U1 Apache-2.0 No Details →
0.4.24 11 Jul 2024 M1 U1 Apache-2.0 No Details →
0.4.23 05 Jul 2024 M1 U1 Apache-2.0 No Details →
0.4.22 06 Jun 2024 M1 U1 Apache-2.0 No Details →
0.4.21 04 Apr 2024 M1 U1 Apache-2.0 No Details →
0.4.20 07 Feb 2024 M1 U1 Apache-2.0 No Details →
0.4.19 18 Jan 2024 M1 U1 Apache-2.0 No Details →
0.4.18 06 Dec 2023 M1 U1 Apache-2.0 No Details →
0.4.17 05 Dec 2023 M1 U1 Apache-2.0 No Details →
0.4.16 03 Nov 2023 M1 U1 Apache-2.0 No Details →
0.4.15 31 Oct 2023 M1 U1 Apache-2.0 No Details →
0.4.14 11 Oct 2023 M1 U1 Apache-2.0 No Details →
0.4.13 22 Aug 2023 M1 U1 Apache-2.0 No Details →
0.4.12 08 Aug 2023 M1 U1 Apache-2.0 No Details →
0.4.11 23 Jun 2023 M1 U1 Apache-2.0 No Details →
0.4.10 26 Apr 2023 M1 U1 Apache-2.0 No Details →
0.4.9 18 Apr 2023 M1 U1 Apache-2.0 No Details →
0.4.8 06 Apr 2023 M1 U1 Apache-2.0 No Details →
0.4.7 03 Apr 2023 M1 U1 Apache-2.0 No Details →
0.5.0 03 Apr 2023 M1 U1 Apache-2.0 No Details →
0.4.0.post1 20 Jan 2023 M1 U1 Apache-2.0 No Details →
0.4.6 01 Nov 2022 M1 U1 Apache-2.0 No Details →
0.4.5 18 May 2022 M1 U1 Apache-2.0 No Details →
0.4.4 09 May 2022 M1 U1 Apache-2.0 No Details →
0.4.3 24 Mar 2022 M1 U1 Apache-2.0 No Details →
0.4.2 11 Nov 2021 M1 U1 Apache-2.0 No Details →
0.4.1 02 Nov 2021 M1 U1 Apache-2.0 No Details →
0.4.0 25 Aug 2021 M1 U1 Apache-2.0 No Details →
0.3.4 24 Jun 2021 M1 U1 Apache-2.0 No Details →
0.3.3 14 Jun 2021 M1 U1 Apache-2.0 No Details →
0.3.2 10 May 2021 M1 U1 Apache-2.0 No Details →
0.3.1 08 Apr 2021 M1 U1 Apache-2.0 No Details →
0.3.0 10 Mar 2021 M1 U1 Apache-2.0 No Details →
0.2.16 10 Feb 2021 M1 U1 Apache-2.0 No Details →
0.2.15 08 Feb 2021 M1 U1 Apache-2.0 No Details →
0.2.14 28 Jan 2021 M1 U1 Apache-2.0 No Details →
0.2.13 16 Dec 2020 M1 U1 Apache-2.0 No Details →
0.2.12 04 Dec 2020 M1 U1 Apache-2.0 No Details →
0.2.11 10 Nov 2020 M1 U1 Apache-2.0 No Details →
0.2.9 04 Nov 2020 M1 U1 Apache-2.0 No Details →
0.2.8 28 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc12 21 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc11 20 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc10 17 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc9 05 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc5 04 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc4 03 Aug 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc3 30 Jul 2020 M1 U1 Apache-2.0 No Details →
0.2.8rc1 29 Jul 2020 M1 U1 Apache-2.0 No Details →
0.2.7 10 Jul 2020 M1 U1 Apache-2.0 No Details →
0.2.6 10 Jul 2020 M1 U1 Apache-2.0 No Details →
0.2.5 10 Jun 2020 M1 U1 Apache-2.0 No Details →
0.2.5a2 20 May 2020 M1 U1 Apache-2.0 No Details →
0.2.5a1 20 May 2020 M1 U1 Apache-2.0 No Details →
0.2.4 20 May 2020 M1 U1 Apache-2.0 No Details →
0.2.3 13 May 2020 M1 U1 Apache-2.0 No Details →
0.2.2 12 May 2020 M1 U1 Apache-2.0 No Details →
0.2.2a4 08 May 2020 M1 U1 Apache-2.0 No Details →
0.2.2a3 07 May 2020 M1 U1 Apache-2.0 No Details →
0.2.2a2 07 May 2020 M1 U1 Apache-2.0 No Details →
0.2.2a1 06 May 2020 M1 U1 Apache-2.0 No Details →
0.2.1 04 May 2020 M1 U1 Apache-2.0 No Details →
0.2.1a1 28 Apr 2020 M1 U1 Apache-2.0 No Details →
0.2.0 02 Apr 2020 M1 U1 Apache-2.0 No Details →
0.1.8 11 Mar 2020 M1 U1 Apache-2.0 No Details →
0.1.7 20 Feb 2020 M1 U1 Apache-2.0 No Details →
0.1.7a1 20 Feb 2020 M1 U1 Apache-2.0 No Details →
0.1.6 14 Feb 2020 M1 U1 Apache-2.0 No Details →
0.1.5 14 Feb 2020 M1 U1 Apache-2.0 No Details →
0.1.4 14 Feb 2020 M1 U1 Apache-2.0 No Details →
0.1.3 01 Nov 2019 M1 U1 Apache-2.0 No Details →
0.1.3b11 29 Oct 2019 M1 U1 Apache-2.0 No Details →
0.1.3b10 18 Oct 2019 M1 U1 Apache-2.0 No Details →
0.1.3b8 17 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b7 13 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b6 12 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b5 12 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b4 10 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b3 10 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b2 10 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.3b1 10 Sep 2019 M1 U1 Apache-2.0 No Details →
0.1.2 09 Sep 2019 M1 U1 — No Details →
0.1.2.dev0 21 Aug 2019 M1 U1 — No Details →
0.1.1 21 Aug 2019 M1 U1 — No Details →
0.1.0 07 Aug 2019 M1 U1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for galaxy-importer

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-5189: Ansible galaxy-importer Path Traversal vulnerability 6.3 medium No fix published 15 Nov 2023
CVE-2023-5189: galaxy-importer Path Traversal Vulnerability in Ansible 6.3 medium No fix published 07 Jul 2026

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 galaxy-importer

Is galaxy-importer safe to use?

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

What is galaxy-importer's Vulert package health score?

Vulert scores galaxy-importer 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 galaxy-importer affected?

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

Which version of galaxy-importer should I use?

0.4.44 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 galaxy-importer have?

2 vulnerabilities are recorded for galaxy-importer in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 galaxy-importer vulnerabilities disclosed?

1 vulnerability was recorded for galaxy-importer in the last 12 months, and the oldest entry in this database dates to 15 Nov 2023. 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 galaxy-importer 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 galaxy-importer for upcoming vulnerabilities?

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