How severe is CVE-2023-6019?

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

Which packages are affected by CVE-2023-6019?

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

How do I fix CVE-2023-6019?

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

How do I detect CVE-2023-6019 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-6019 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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

Yes. There are 4 known exploit references for CVE-2023-6019, including 1 documented proof-of-concept exploit on Exploit-DB and 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-6019?

CVE-2023-6019 has an EPSS (Exploit Prediction Scoring System) score of 74.6%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2023-6019?

CVE-2023-6019 is classified as OS Command Injection (CWE-78). This weakness type 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.

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

A Metasploit module references CVE-2023-6019, which lowers the barrier to weaponization. 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-6019 published, and has it been updated?

CVE-2023-6019 was published on November 16, 2023 and was last updated on October 28, 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-6019 — ray

CRITICAL

CVE-2023-6019 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in ray. 4 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 Command Injection in cpu_profile Parameter

Also known asGHSA-h3xg-wv58-5p43PYSEC-2026-519

Published

Nov 16, 2023

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

74.6%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% 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

A command injection existed in Ray's cpu_profile URL parameter allowing attackers to execute os commands on the system running the ray dashboard remotely 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.

EDB-51978webappspython

Ray OS v2.6.3 - Command Injection RCE(Unauthorized)

by Fire_Wolf · Apr 12, 2024

Exploit-DB Source

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-6019 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-6019 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-78OS Command Injection

Weaponization

Timeline

Disclosed

Nov 16, 2023

First exploit

Apr 12, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2023-6019

GHSA-h3xg-wv58-5p43

PYSEC-2026-519

References

Advisorygithub.com · CVE 2023 6019.json Advisorynvd.nist.gov · CVE 2023 6019 Webhuntr.com · d0290f3c b302 4161 89f2 c13bb28b4cfe Webgithub.com · ray Webgithub.com · ray 2.8.1 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 verifiedOct 28, 2026

CVE-2023-6019 — 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

Frequently Asked Questions

Is CVE-2023-6019 in your dependencies?