# CVE-2023-48022: Ray has arbitrary code execution via jobs submission API

> Remote attackers can execute arbitrary code via the job submission API in Ray, requiring network isolation or token authentication for mitigation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Nov 2023
- **Updated:** 17 Dec 2025
- **Also known as:** CVE-2024-57000, GHSA-6wgj-66m2-xxp2, MINI-272g-gqhc-wpg6, PYSEC-2026-517

## What is CVE-2023-48022?

CVE-2023-48022 is a critical server-side request forgery vulnerability in n/a, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.)

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2023-48022?

3 open source packages ship an affected version, including ray. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ray` | PyPI | All versions to 2.49.2 | None |
| `ray` | PyPI | All versions to 2.49.2 | None |
| `ray` | PyPI | All versions to 2.49.2 | None |

Products: Anyscale Ray.

## How do I fix CVE-2023-48022?

Change a configuration setting.

## Is CVE-2023-48022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-48022 exists.

Public exploit code:

- ShadowRay RCE POC (CVE-2023-48022) (github_poc): https://github.com/jakabakos/ShadowRay-RCE-PoC-CVE-2023-48022
- CVE-2023-48022 exploit modified from Bishop Fox work (github_poc): https://github.com/0x656565/CVE-2023-48022
- Ray Agent Job RCE (metasploit)
- Anyscale Ray - Remote Code Execution (nuclei): http/cves/2023/CVE-2023-48022.yaml

## Other vulnerabilities in n/a

- [CVE-2025-62593](https://insights.sbomify.com/CVE-2025-62593/): Ray-Project Ray Code Injection (critical 9.4, exploited in the wild)
- [CVE-2023-48023](https://insights.sbomify.com/CVE-2023-48023/): Server-side request forgery in n/a (critical 9.1)
- [CVE-2026-41486](https://insights.sbomify.com/CVE-2026-41486/): Ray: Remote Code Execution via Parquet Arrow Extension Type Deserialization (high 8.9)
- [CVE-2026-32981](https://insights.sbomify.com/CVE-2026-32981/): Ray Dashboard <= 2.8.0 Path Traversal Leading to Local File Disclosure (high 8.7)
- [CVE-2026-57516](https://insights.sbomify.com/CVE-2026-57516/): Ray < 2.56.0 Unsafe Deserialization RCE via WebDataset Reader (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48022 and fix it if it is affected.

What it is: CVE-2023-48022 is a critical server-side request forgery vulnerability in n/a, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-48022 exists.

Affected packages and fixed versions:
- ray (PyPI): affected all versions up to 2.49.2; no fix listed
- ray (PyPI): affected all versions up to 2.49.2; no fix listed
- ray (PyPI): affected all versions up to 2.49.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-48022/ (Markdown: https://insights.sbomify.com/CVE-2023-48022/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-48022
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-48022
- OSV: https://osv.dev/vulnerability/CVE-2023-48022

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-48022/
Summaries are generated and may contain mistakes; the official description above is the record.