CVEs.
Vulnerabilities published in the last two years in software made by the companies on the wall: clients, SDKs, agents and self-hosted editions. A CVE here does not mean the hosted service was affected or breached.
NVD data refreshed 36 min ago
Severity of matching CVEs
CVSS base severity, as scored in NVD
- Critical
- 120%
- High
- 360%
- Medium
- 120%
- Low or not scored
- 00%
- Matching CVEs
- 5
- Last two years
- Critical
- 1
- CVSS 9.0 and above
- High
- 3
- CVSS 7.0 to 8.9
- Known exploited
- 1
- On CISA's KEV list
Matching CVEs published
By month, last two years
Peak 1 · November 2025
- Total: 5
- December 2024: 0
- January 2025: 0
- February 2025: 0
- March 2025: 0
- April 2025: 0
- May 2025: 0
- June 2025: 0
- July 2025: 0
- August 2025: 0
- September 2025: 0
- October 2025: 0
- November 2025: 1
- December 2025: 0
- January 2026: 0
- February 2026: 1
- March 2026: 1
- April 2026: 0
- May 2026: 1
- June 2026: 0
- July 2026: 1
- August 2026: 0
- September 2026: 0
- October 2026: 0
- November 2026: 0
Most CVEs
In each company's software, last two years
Matching CVEs
- 8.6High
CVE-2026-57516 (opens in a new tab)
Ray prior to 2.56.0 contains an unsafe deserialization vulnerability in the WebDataset reader that allows attackers to achieve remote code execution by supplying a malicious tar archive to the read_webdataset() function. The _default_decoder() function in webdataset_datasource.py unconditionally calls pickle.loads() on tar entries with .pkl/.pickle extensions and torch.load() with weights_only=False on .pt/.pth entries, executing arbitrary code inside Ray remote workers on every worker that processes the malicious archive.
Anyscale· Jul 1, 2026
- 8.9High
CVE-2026-41486 (opens in a new tab)
Ray is an AI compute engine. From version 2.54.0 to before version 2.55.0, Ray Data registers custom Arrow extension types (ray.data.arrow_tensor, ray.data.arrow_tensor_v2, ray.data.arrow_variable_shaped_tensor) globally in PyArrow. When PyArrow reads a Parquet file containing one of these extension types, it calls __arrow_ext_deserialize__ on the field's metadata bytes. Ray's implementation passes these bytes directly to cloudpickle.loads(), achieving arbitrary code execution during schema parsing, before any row data is read. This issue has been patched in version 2.55.0.
Anyscale· May 8, 2026
- 8.7High
CVE-2026-32981 (opens in a new tab)
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.
Anyscale· Mar 17, 2026
- 6.5Med
CVE-2026-27482 (opens in a new tab)
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.
Anyscale· Feb 21, 2026
- 9.4Crit
CVE-2025-62593 (opens in a new tab)Known exploited
Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer ru
Anyscale· Nov 26, 2025
Public information only
Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.
Sources
- National Vulnerability Database (opens in a new tab): CVE IDs, descriptions, publication dates and CVSS severity, published by the U.S. government (NIST)
- CISA Known Exploited Vulnerabilities catalog (opens in a new tab): the "Known exploited" flag
How fresh it is
- New and changed CVEs: pulled from NVD every two hours; last run 36 min ago
- Known-exploited flags: updated from CISA in the same run
- Window: the last two years; older entries drop off automatically
Source: the U.S. National Vulnerability Database, refreshed daily, with the known-exploited flag from CISA's KEV catalog. Descriptions are NVD's. A CVE is listed under a company when NVD names that company's product as affected, or when the company's own CVE authority assigned it; companies whose names are common words are matched only by explicit rules, so some CVEs will be missing. This product uses NVD data but is not endorsed or certified by the NVD. CVE is a registered trademark of The MITRE Corporation.
statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.