# CVE-2026-27482: Ray: Dashboard DELETE endpoints allow unauthenticated browser-triggered DoS (Serve shutdown / job deletion)

> Unauthenticated DELETE requests in Ray dashboard allow attackers to shut down Serve or delete jobs via drive-by attacks if the dashboard is exposed.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** ECHO-0e02-c16f-6496, GHSA-q5fh-2hc8-f6rq, MINI-cv95-83v9-fqmc, MINI-hf8g-882v-x575, PYSEC-2026-2271

## What is CVE-2026-27482?

CVE-2026-27482 is a medium-severity missing authorization vulnerability in ray-project ray, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Ray is an AI compute engine. In versions 2.53.0 and below, thedashboard HTTP server blocks browser-origin POST/PUT but does not cover DELETE, and key DELETE endpoints are unauthenticated by default. If the dashboard/agent is reachable (e.g., --dashboard-host=0.0.0.0), a web page via DNS rebinding or same-network access can issue DELETE requests that shut down Serve or delete jobs without user interaction. This is a drive-by availability impact. The fix for this vulnerability is to update to Ray 2.54.0 or higher.

Weakness: CWE-396 (Declaration of Catch for Generic Exception)

## Which versions are affected by CVE-2026-27482?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ray` | PyPI | All versions | 2.54.0 |
| `ray` | PyPI | All versions | 2.54.0 |
| `ray` | PyPI | All versions | 2.54.0 |

Products: Anyscale Ray.

## How do I fix CVE-2026-27482?

Upgrade ray to 2.54.0 or later.

## Is CVE-2026-27482 being exploited?

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

## Other vulnerabilities in ray-project ray

- [CVE-2025-62593](https://insights.sbomify.com/CVE-2025-62593/): Ray-Project Ray Code Injection (critical 9.4, exploited in the wild)
- [CVE-2023-48022](https://insights.sbomify.com/CVE-2023-48022/): Ray has arbitrary code execution via jobs submission API (critical 9.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27482 and fix it if it is affected.

What it is: CVE-2026-27482 is a medium-severity missing authorization vulnerability in ray-project ray, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27482 exists.

Affected packages and fixed versions:
- ray (PyPI): affected all versions; fixed in 2.54.0
- ray (PyPI): affected all versions; fixed in 2.54.0
- ray (PyPI): affected all versions; fixed in 2.54.0

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-2026-27482/ (Markdown: https://insights.sbomify.com/CVE-2026-27482/index.md)
```

## Sources

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

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