How severe is CVE-2023-48022?

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

Which packages are affected by CVE-2023-48022?

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

How do I fix CVE-2023-48022?

No fixed version has been published for CVE-2023-48022 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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

Yes. There are 4 known exploit references for CVE-2023-48022, including 3 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-48022?

CVE-2023-48022 has an EPSS (Exploit Prediction Scoring System) score of 92.2%, 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.

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

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

CVE-2023-48022 was published on November 28, 2023 and was last updated on April 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

CVE-2023-48022

CRITICAL

Ray has arbitrary code execution via jobs submission API

Also known asGHSA-6wgj-66m2-xxp2

Published

Nov 28, 2023

Updated

Apr 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

92.2%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

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.

Blast Radius

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

Anyscale Ray 2.6.3 and 2.8.0 allows a remote attacker to execute arbitrary code via the job submission API. NOTE: the vendor's position is that this report is irrelevant because Ray, as stated in its documentation, is not intended for use outside of a strictly controlled network environment. (Also, within that environment, customers at version 2.52.0 and later can choose to use token authentication.)

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ray`	all versions	No fix

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.

Anyscale Ray 2.6.3 and 2.8.0 allows a remote attacker to execute arbitra…

bishopfox.comNVDDec 2023

Anyscale Ray 2.6.3 and 2.8.0 allows a remote attacker to execute arbitra…

github.comGithubMar 2024

Anyscale Ray 2.6.3 and 2.8.0 allows a remote attacker to execute arbitra…

github.comMetasploitAug 2024

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-48022 in your stack?

O3 detects CVE-2023-48022 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works