How severe is CVE-2023-6020?

CVE-2023-6020 has a CVSS score of 9.3/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-6020?

CVE-2023-6020 affects the following packages: ray (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2023-6020?

Update ray to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6020 is resolved across your whole dependency graph.

How do I detect CVE-2023-6020 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ray, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-6020 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2023-6020 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2023-6020, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-6020?

CVE-2023-6020 has an EPSS (Exploit Prediction Scoring System) score of 14.7%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2023-6020?

CVE-2023-6020 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2023-6020?

A Nuclei detection template exists for CVE-2023-6020, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-6020 published, and has it been updated?

CVE-2023-6020 was published on November 16, 2023 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2023-6020 — ray

CRITICAL

CVE-2023-6020 is a critical-severity (CVSS 9.3) CWE-862 vulnerability in ray. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for ray — see the affected versions and patch details below.

Ray Missing Authorization vulnerability

Also known asPYSEC-2026-516

Published

Nov 16, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

14.7%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍ray

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

LFI in Ray's /static/ directory allows attackers to read any file on the server without authentication. The issue is fixed in version 2.8.1+. Ray maintainers response can be found here: https://www.anyscale.com/blog/update-on-ray-cves-cve-2023-6019-cve-2023-6020-cve-2023-6021-cve-2023-48022-cve-2023-48023

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ray`	all versions	2.8.1`pip install --upgrade 'ray==2.8.1'`

Affected Products

1 product · 1 configurations

Application

rayray_project

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

LFI in Ray's /static/ directory allows attackers to read any file on the…

huntr.comNVDNov 2023

Report on github.com

github.comMetasploitAug 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ray, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ray to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6020 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How to detect CVE-2023-6020

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2023-6020 -u https://target

Template: Ray Static File - Local File Inclusion
Severity: high
Impact: Unauthenticated attackers can read any file on the server via path traversal in the /static/ directory, potentially exposing sensitive configuration files and credentials.
Remediation: Update Ray to a patched version that restricts static file access.

Template by ProjectDiscovery nuclei-templates (byt3bl33d3r), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-6020 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

CWE Classification

Weaponization

OpenSSF Scorecard

Package health score

ray

5.7/10

Code-Review9/10

Maintained10/10

Branch-Protection8/10

Assessed Oct 19, 2026

Timeline

Disclosed

Nov 16, 2023

First exploit

Nov 24, 2023

Last updated

Sep 10, 2026

Identifiers

CVE-2023-6020

PYSEC-2026-516

References

Advisorynvd.nist.gov · CVE 2023 6020 Webgithub.com · ray Webgithub.com · ray 2.8.1 Webhuntr.com · 83dd8619 6dc3 4c98 8f1b e620fedcd1f6 Webanyscale.com · update on ray cves cve 2023 6019 cve 2023 6020 cve 2023 6021 cve 2023 48022 cve 2023 48023

Related vulnerabilities

This CVE is critical severity; 3 of 8 other CVEs affecting ray are rated as high or higher (top: critical).

CVE-2026-57516CVE-2026-41486CVE-2026-32981CVE-2026-27482CVE-2025-34351CVE-2025-62593CVE-2025-1979CVE-2023-48022

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

CVE-2023-6020 — ray

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2023-6020

Frequently Asked Questions

Is CVE-2023-6020 in your dependencies?