Quick answers
- Is CVE-2023-6021 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-6021 being exploited in the wild.
- How severe is CVE-2023-6021?
- Low severity, with a CVSS score of 3, published 29 June 2026.
- Which products and versions are affected?
- ray (PyPI) ECOSYSTEM:introduced=0,fixed=2.8.1.
- Is there a fix for CVE-2023-6021?
- Yes. ray (PyPI): upgrade to 2.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2023-6021 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2023-6021?
- Check whether you run ray (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ray (PyPI): upgrade to 2.8.1 or later
pip install "ray>=2.8.1"
Technical details
The vulnerability is a local file inclusion (LFI) in Ray's log API endpoint caused by improper path validation (CWE-22: Improper Limitation of a Pathname to a Restricted Directory, and CWE-29: Path Traversal). The vulnerable endpoint does not properly sanitize user-supplied file path parameters, allowing attackers to traverse directories using sequences like `../` to access files outside the intended log directory. The attack requires only network access to the Ray API endpoint and no authentication; an attacker can directly read arbitrary files on the host system. The vulnerability affects all versions prior to 2.8.1, which contains the fix.
Affected products
- Ray Ray prior to 2.8.1
Identifiers
- CVE-2023-6021
- GHSA-3pww-qvr8-6mhp
- PYSEC-2026-515
Timeline
- 2023-11-16: disclosed
- 2023-11-16: patched: Fix released in Ray 2.8.1