How severe is CVE-2023-6021?

CVE-2023-6021 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2023-6021?

Affected package information for CVE-2023-6021 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2023-6021?

No patch has shipped for CVE-2023-6021 yet — track the ray_project ray advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2023-6021 across my infrastructure?

Inventory every ray_project ray deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2023-6021?

O3 detects and blocks CVE-2023-6021 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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

Yes. There are 1 known exploit references for CVE-2023-6021, including 1 in-the-wild exploitation 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-6021?

CVE-2023-6021 has an EPSS (Exploit Prediction Scoring System) score of 37.1%, placing it in the 98th 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-6021?

CVE-2023-6021 is classified as CWE-29 (CWE-29), Path Traversal (CWE-22). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2023-6021?

CVE-2023-6021 affects ray_project ray. Check the affected-products list on this page against your deployed version to confirm exposure.

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

A Nuclei detection template exists for CVE-2023-6021, 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-6021 published, and has it been updated?

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

CVE-2023-6021

HIGH

LFI in Ray's log API endpoint 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:…

Published

Nov 16, 2023

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

37.1%probability of exploitation in next 30 days

Moderate Risk98th percentile-50.24%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

LFI in Ray's log API endpoint 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 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 log API endpoint allows attackers to read any file on the s…

huntr.comNVDNov 2023

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every ray_project ray deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2023-6021 yet — track the ray_project ray advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2023-6021 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2023-6021. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2023-6021 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2023-6021 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2023-6021

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2023-6021 being exploited in your environment?