VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ray: vulnerability history, versions and safety

ray is a package in the PyPI ecosystem. Vulert records 23 vulnerabilities for it across 120 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
23 vulnerabilities recorded C7 H3 M2 U11
i
6 with no fix published

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

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

Most recent disclosure 24 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ray vulnerabilities

Vulert verdict on ray 2.59.0 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • 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 2.59.0 — affected i
  • Vulnerabilities on record 23 over 2 years · 16 in the last year i
  • Latest disclosure 24 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 6 i
  • Depended on by 641 packages i
  • Stars 44,099 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 ray, 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
2.58.1 21 Oct 2026 C3 U4 Apache-2.0 No Details →
2.57.1 21 Oct 2026 C3 U4 Apache-2.0 No Details →
2.59.0 02 Oct 2026 C3 U4 Apache-2.0 No Details →
2.58.0 23 Aug 2026 C3 U4 Apache-2.0 No Details →
2.57.0 11 Aug 2026 C3 U4 Apache-2.0 No Details →
2.56.1 17 Jul 2026 C3 U4 Apache-2.0 No Details →
2.56.0 29 Jun 2026 C3 U4 Apache-2.0 No Details →
2.55.1 22 Apr 2026 H1 U1 Apache-2.0 Yes Details →
2.55.0 15 Apr 2026 H1 U1 Apache-2.0 Yes Details →
2.54.1 25 Mar 2026 H2 U1 Apache-2.0 Yes Details →
2.54.0 18 Feb 2026 H2 U2 Apache-2.0 No Details →
2.53.0 20 Dec 2025 H2 M1 U3 Apache-2.0 No Details →
2.51.2 29 Nov 2025 C1 H2 M1 U5 Apache-2.0 No Details →
2.52.1 28 Nov 2025 H2 M1 U3 Apache-2.0 No Details →
2.52.0 21 Nov 2025 C1 H2 M1 U4 Apache-2.0 No Details →
2.51.1 01 Nov 2025 C2 H2 M1 U5 Apache-2.0 No Details →
2.51.0 29 Oct 2025 C2 H2 M1 U5 Apache-2.0 No Details →
2.50.1 18 Oct 2025 C2 H2 M1 U5 Apache-2.0 No Details →
2.50.0 10 Oct 2025 C2 H2 M1 U5 Apache-2.0 No Details →
2.49.2 19 Sep 2025 C3 H2 M1 U6 Apache-2.0 No Details →
2.49.1 03 Sep 2025 C3 H2 M1 U6 Apache-2.0 No Details →
2.49.0 26 Aug 2025 C3 H2 M1 U6 Apache-2.0 No Details →
2.48.0 18 Jul 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.47.1 17 Jun 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.47.0 11 Jun 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.46.0 07 May 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.45.0 29 Apr 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.44.1 27 Mar 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.44.0 21 Mar 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.43.0 27 Feb 2025 C3 H1 M1 U6 Apache-2.0 No Details →
2.42.1 11 Feb 2025 C3 H1 M2 U7 Apache-2.0 No Details →
2.42.0 04 Feb 2025 C3 H1 M2 U7 Apache-2.0 No Details →
2.41.0 23 Jan 2025 C3 H1 M2 U7 Apache-2.0 No Details →
2.40.0 03 Dec 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.39.0 12 Nov 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.38.0 23 Oct 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.37.0 24 Sep 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.36.1 23 Sep 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.36.0 16 Sep 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.35.0 27 Aug 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.34.0 30 Jul 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.33.0 25 Jul 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.32.0 10 Jul 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.32.0rc0 03 Jul 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.31.0 26 Jun 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.30.0 20 Jun 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.24.0 06 Jun 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.23.0 22 May 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.22.0 14 May 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.21.0 08 May 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.20.0 01 May 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.12.0 25 Apr 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.11.0 17 Apr 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.10.0 21 Mar 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.9.3 22 Feb 2024 C4 H1 M2 U7 Apache-2.0 No Details →
2.9.2 05 Feb 2024 C3 H1 M2 U7 Apache-2.0 No Details →
2.9.1 19 Jan 2024 C3 H1 M2 U7 Apache-2.0 No Details →
2.9.0 21 Dec 2023 C3 H1 M2 U7 Apache-2.0 No Details →
2.7.2 04 Dec 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.8.1 01 Dec 2023 C3 H1 M2 U7 Apache-2.0 No Details →
2.8.0 03 Nov 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.7.1 09 Oct 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.7.0 17 Sep 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.7.0rc0 02 Sep 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.6.3 15 Aug 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.6.2 03 Aug 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.6.1 24 Jul 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.6.0 21 Jul 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.5.1 21 Jun 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.5.0 08 Jun 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.4.0 25 Apr 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.3.1 25 Mar 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.3.0 24 Feb 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.3.0rc0 23 Feb 2023 C6 H2 M2 U11 Apache-2.0 No Details →
2.2.0 13 Dec 2022 C6 H2 M2 U11 Apache-2.0 No Details →
2.1.0 08 Nov 2022 C6 H2 M2 U11 Apache-2.0 No Details →
2.0.1 22 Oct 2022 C6 H2 M2 U11 Apache-2.0 No Details →
2.0.0 23 Aug 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.13.0 09 Jun 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.12.1 16 May 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.11.1 29 Apr 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.12.0 14 Apr 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.11.0 09 Mar 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.10.0 04 Feb 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.9.2 11 Jan 2022 C6 H2 M2 U11 Apache-2.0 No Details →
1.9.1 22 Dec 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.9.0 03 Dec 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.8.0 02 Nov 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.7.1 22 Oct 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.7.0 07 Oct 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.6.0 23 Aug 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.5.2 12 Aug 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.5.1 31 Jul 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.5.0 26 Jul 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.4.1 30 Jun 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.4.0 07 Jun 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.3.0 22 Apr 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.2.0 13 Feb 2021 C6 H2 M2 U11 Apache-2.0 No Details →
1.1.0 24 Dec 2020 C6 H2 M2 U11 Apache-2.0 No Details →
1.0.1 10 Nov 2020 C6 H2 M2 U11 Apache-2.0 No Details →
1.0.0 30 Sep 2020 C6 H2 M2 U11 — No Details →
0.8.7 13 Aug 2020 C6 H2 M2 U11 — No Details →
0.8.6 24 Jun 2020 C6 H2 M2 U11 — No Details →
0.8.5 07 May 2020 C6 H2 M2 U11 — No Details →
0.8.4 02 Apr 2020 C6 H2 M2 U11 — No Details →
0.8.3 25 Mar 2020 C6 H2 M2 U11 — No Details →
0.8.2 24 Feb 2020 C6 H2 M2 U11 — No Details →
0.8.1 27 Jan 2020 C6 H2 M2 U11 — No Details →
0.8.0 17 Dec 2019 C6 H2 M2 U11 — No Details →
0.7.7 16 Dec 2019 C6 H2 M2 U11 — No Details →
0.7.6 24 Oct 2019 C6 H2 M2 U11 — No Details →
0.7.5 25 Sep 2019 C6 H2 M2 U11 — No Details →
0.7.4 05 Sep 2019 C6 H2 M2 U11 — No Details →
0.7.3 04 Aug 2019 C6 H2 M2 U11 — No Details →
0.7.2 03 Jul 2019 C6 H2 M2 U11 — No Details →
0.7.1 11 Jun 2019 C6 H2 M2 U11 — No Details →
0.7.0 18 May 2019 C6 H2 M2 U11 — No Details →
0.6.6 19 Apr 2019 C6 H2 M2 U11 — No Details →
0.6.5 25 Mar 2019 C6 H2 M2 U11 — No Details →
0.6.4 06 Mar 2019 C6 H2 M2 U11 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 4
  • 2025 5
  • 2026 14

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

03 Vulnerabilities

Recorded vulnerabilities for ray

The 5 most severe of 23 vulnerabilities recorded for this package

Search all 23 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-48022: Ray Package Arbitrary Code Execution via Job Submission API 9.8 critical No fix published 29 Jun 2026
CVE-2023-6019: Ray OS Command Injection Vulnerability 9.8 critical 2.8.1 29 Jun 2026
CVE-2023-6019: Ray OS Command Injection vulnerability 9.8 critical 2.8.1 16 Nov 2023
CVE-2024-57000: Command Injection Vulnerability in Ray 9.8 critical No fix published 12 Feb 2025
CVE-2023-48022: Ray Package Arbitrary Code Execution via Job Submission API 9.8 critical No fix published 28 Nov 2023

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 ray

Is ray safe to use?

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

What is ray's Vulert package health score?

Vulert scores ray 50/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 ray affected?

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

Which version of ray should I use?

2.59.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 ray have?

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

16 vulnerabilities were recorded for ray in the last 12 months, and the oldest entry in this database dates to 16 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 ray 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 ray for upcoming vulnerabilities?

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