VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

galaxy-app: vulnerability history, versions and safety

galaxy-app is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 0 release, from Jun 2018 to May 2022. 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
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 galaxy-app vulnerabilities

Vulert verdict on galaxy-app 26.1.1 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 26.1.1 — unaffected i
  • Vulnerabilities on record 2 over 3 years · 0 in the last year i
  • Latest disclosure 14 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Stars 1,874 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 months ago i
  • Licence MIT 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-app, 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
26.1.1 04 Aug 2026 none MIT — Details →
26.1.0 03 Aug 2026 none MIT — Details →
26.0.1 06 Jun 2026 none MIT — Details →
26.0.0 09 Apr 2026 none MIT — Details →
26.0.1.dev0 09 Apr 2026 none MIT — Details →
25.1.2 09 Mar 2026 none non-standard — Details →
25.1.1 03 Feb 2026 none non-standard — Details →
25.1.0 17 Dec 2025 none non-standard — Details →
25.1.0.dev0 13 Dec 2025 none non-standard — Details →
25.0.4 18 Nov 2025 none non-standard — Details →
25.0.3 23 Sep 2025 none non-standard — Details →
25.0.2 13 Aug 2025 none non-standard — Details →
25.0.1 21 Jun 2025 none non-standard — Details →
25.0.0 18 Jun 2025 none non-standard — Details →
24.2.4 17 Jun 2025 none non-standard — Details →
24.2.3 16 Mar 2025 none non-standard — Details →
24.2.2 08 Mar 2025 none non-standard — Details →
24.2.1 28 Feb 2025 none non-standard — Details →
24.2.0 12 Feb 2025 none non-standard — Details →
24.1.4 11 Dec 2024 none non-standard — Details →
24.1.3 29 Oct 2024 none non-standard — Details →
24.1.2 25 Sep 2024 none non-standard — Details →
24.1.1 03 Jul 2024 none non-standard — Details →
24.0.3 28 Jun 2024 none non-standard — Details →
24.0.2 07 May 2024 none non-standard — Details →
24.0.1 02 May 2024 none non-standard — Details →
24.0.0 03 Apr 2024 none non-standard — Details →
23.2.1 22 Feb 2024 none non-standard — Details →
23.1.0.dev0 12 Feb 2024 none non-standard — Details →
23.1.4 04 Jan 2024 none non-standard — Details →
23.1.3 01 Dec 2023 none non-standard — Details →
23.1.2 29 Nov 2023 none non-standard — Details →
23.1.1 23 Oct 2023 none non-standard — Details →
23.0.6 23 Oct 2023 none non-standard — Details →
23.0.5 30 Jul 2023 none non-standard — Details →
23.0.4 30 Jun 2023 none non-standard — Details →
23.0.3 26 Jun 2023 none non-standard — Details →
23.0.2 13 Jun 2023 none non-standard — Details →
23.0.1 08 Jun 2023 none non-standard — Details →
22.1.1 22 Aug 2022 none non-standard — Details →
21.9.0 02 Nov 2021 none non-standard — Details →
20.9.0 15 Oct 2020 none non-standard — Details →
20.5.0 04 Jul 2020 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 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 galaxy-app

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000516: Galaxy App Cross-Site Scripting Vulnerability 6.1 medium 14.10.1 26 Jun 2018
CVE-2018-1000516: Galaxy App Cross-Site Scripting (XSS) Vulnerability 6.1 medium 14.10.1 14 May 2022

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-app

Is galaxy-app safe to use?

Vulert records 2 vulnerabilities for galaxy-app in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

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

Vulert scores galaxy-app 81/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 galaxy-app affected?

No. 26.1.1, 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 galaxy-app should I use?

26.1.1 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-app have?

2 vulnerabilities are recorded for galaxy-app 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-app vulnerabilities disclosed?

0 vulnerabilities were recorded for galaxy-app in the last 12 months, and the oldest entry in this database dates to 26 Jun 2018. 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-app 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-app for upcoming vulnerabilities?

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