CVE-2026-32981
Anyscale Ray path traversal
- Published17 Mar 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:19712
- https://access.redhat.com/errata/RHSA-2026:24977
- https://access.redhat.com/errata/RHSA-2026:42644
- https://access.redhat.com/errata/RHSA-2026:5809
- https://access.redhat.com/errata/RHSA-2026:6761
- https://access.redhat.com/errata/RHSA-2026:6762
- https://access.redhat.com/security/cve/CVE-2026-32981
- https://bugzilla.redhat.com/show_bug.cgi?id=2448440
- https://github.com/ray-project/ray
- https://packetstorm.news/files/id/215801/
and 2 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-32981 being actively exploited?
CVE-2026-32981 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.03%.
How severe is CVE-2026-32981?
CVE-2026-32981 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 1.03% probability of exploitation.
Which products are affected by CVE-2026-32981?
Affected products include Anyscale Ray.
How do I fix CVE-2026-32981?
Upgrade affected software to a fixed version, for example Anyscale Ray 2.8.1 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-32981 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.