cve.bz

CVE-2026-32981 anyscale ray: Path traversal

8.7 highExploit referenceEPSS 1.1%Fix available

High (8.7) in anyscale ray. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in ray 2.8.1.

On this page
A path traversal vulnerability was identified in Ray Dashboard (default port 8265) in Ray versions prior to 2.8.1. Due to improper validation and sanitization of user-supplied paths in the static file handling mechanism, an attacker can use traversal sequences (e.g., ../) to access files outside the intended static directory, resulting in local file disclosure.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
1.1% (unchanged from 1.0% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 65th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-03-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • ray (PyPI): fixed in 2.8.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-32981 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32981?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32981?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32981 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ray-project Raybefore 2.8.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j3mh-qmjj-xp83PyPIray<2.8.12.8.1
PYSEC-2026-130PyPIray<2.8.12.8.1

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat AI Inference Server 3.2rhaiis/vllm-cuda-rhel9:1774351144Fixed 2026-03-25RHSA-2026:5809
Red Hat AI Inference Server 3.2rhaiis/model-opt-cuda-rhel9:1774547384Fixed 2026-04-07RHSA-2026:6761
Red Hat AI Inference Server 3.2rhaiis/vllm-rocm-rhel9:1775252598Fixed 2026-04-07RHSA-2026:6762
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1780078312Fixed 2026-06-10RHSA-2026:24977
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9:1780078429Fixed 2026-06-10RHSA-2026:24977
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9:1780078632Fixed 2026-06-10RHSA-2026:24977
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9:1780078416Fixed 2026-06-10RHSA-2026:24977
Red Hat OpenShift AI 2.25rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9:1780417775Fixed 2026-06-10RHSA-2026:24977
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9:1780069146Fixed 2026-06-10RHSA-2026:24977
Red Hat OpenShift AI 2.25rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9:1780078413Fixed 2026-06-10RHSA-2026:24977
Red Hat AI Inference Serverrhaiis-preview/vllm-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-aws-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-azure-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-cuda-rhel9Affected
Red Hat Enterprise Linux AI (RHEL AI) 3rhelai3/bootc-gcp-cuda-rhel9Affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-agent-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-controller-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-router-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-kserve-storage-initializer-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-vllm-gaudi-rhel9Affected
16 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-32981.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON