Vulnerability Database · PyPI · ray · Version

ray 1.3.0

1.3.0 is affected by 21 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.59.0.

Critical 12 High 4 Medium 3 Low 0 Unrated 2

Released 22 Apr 2021 Licence Apache-2.0 Also known from other sources 21 Newer releases 124 Database updated 23/Oct/2026

Release and licence data published by PyPI. 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 Vulnerabilities affecting this version

ray 1.3.0 vulnerabilities

21 vulnerabilities cover ray 1.3.0. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2023-6019: Ray OS Command Injection Vulnerability 9.8 critical 2.8.1 29 Jun 2026
CVE-2023-48022: Ray Package Arbitrary Code Execution via Job Submission API 9.8 critical No fix published 29 Jun 2026
CVE-2023-48022: Ray Package Arbitrary Code Execution via Job Submission API 9.8 critical No fix published 28 Nov 2023
CVE-2023-6019: Ray OS Command Injection vulnerability 9.8 critical 2.8.1 16 Nov 2023
CVE-2025-62593: Ray Critical RCE Vulnerability via DNS Rebinding in Safari & Firefox 9.4 critical 2.52.0 29 Jun 2026
CVE-2025-62593: Ray Critical RCE Vulnerability via DNS Rebinding in Safari & Firefox 9.4 critical 2.52.0 26 Nov 2025
CVE-2023-6021: Ray Path Traversal Vulnerability in Ray Package 9.3 critical 2.8.1 29 Jun 2026
CVE-2023-6020: Ray Package LFI Vulnerability Allows Unauthorized File Access 9.3 critical 2.8.1 29 Jun 2026
CVE-2025-34351: Ray Package Token Authentication Disabled by Default 9.3 critical No fix published 29 Jun 2026
CVE-2025-34351: Ray Package Token Authentication Disabled by Default 9.3 critical No fix published 27 Nov 2025
CVE-2023-6020: Ray Missing Authorization vulnerability 9.3 critical 2.8.1 16 Nov 2023
CVE-2023-6021: Ray Path Traversal vulnerability in ray 9.3 critical 2.8.1 16 Nov 2023
CVE-2026-57516: Ray Package Arbitrary Code Execution via Unsafe Deserialization 8.8 high 2.56.0 24 Jul 2026
CVE-2026-41486: Ray Package Arbitrary Code Execution Vulnerability 8.8 high No fix published 08 May 2026
CVE-2026-32981: Ray Package Path Traversal Vulnerability in Ray Dashboard 7.5 high 2.8.1 17 Mar 2026
CVE-2026-32981: Path Traversal Vulnerability in Ray Package Allows Local File Disclosure 7.5 high 2.8.1 17 Mar 2026
CVE-2026-27482: Ray Package Unauthenticated DELETE Requests Vulnerability 6.5 medium 2.54.0 21 Feb 2026
CVE-2025-1979: Ray Package Vulnerable to Sensitive Information Logging 6.4 medium 2.43.0 06 Mar 2025
CVE-2026-27482: Ray Package Unauthenticated DELETE Endpoints Allow Browser-Triggered DoS 5.9 medium 2.54.0 20 Feb 2026
CVE-2026-57516: Ray Package Unsafe Deserialization Vulnerability Leading to Remote Code Execution N/A unrated 2.56.0 01 Jul 2026
CVE-2025-1979: Ray Package Vulnerability Exposes Redis Password in Logs N/A unrated 64a2e4010522d60b90c389634f24df77b603d85d 06 Mar 2025

Looking for another version, or everything Vulert holds for ray?

All versions → Full vulnerability list →

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 1.3.0

Is ray 1.3.0 vulnerable?

Yes. 21 vulnerabilities in the Vulert database cover ray 1.3.0: 12 critical, 4 high, 3 medium and 0 low, plus 2 not yet rated. The upgrade Vulert recommends is 2.59.0, and each entry above names the fixed version to move to.

Which version of ray should I use instead of 1.3.0?

2.59.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 1.3.0 the latest release of ray?

No. 1.3.0 was published 22 Apr 2021, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.