⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5.9

How to Fix CVE-2026-27482: Declaration of catch for generic exception in ray

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27482 is a declaration of catch for generic exception in ray-project ray. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity5.9 (Medium)
Actively exploited?No public listing in CISA KEV
Affectedray < 2.54.0
Fixed inSee vendor advisory
Type (CWE)CWE-396: Declaration of Catch for Generic Exception

What is CVE-2026-27482?

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. The CVSS base score is 5.9 (Medium). The official advisory is at https://github.com/ray-project/ray/security/advisories/GHSA-q5fh-2hc8-f6rq.

Am I affected?

Check the version of ray you are running and compare it against the Affected row above (ray < 2.54.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s ray 2>/dev/null | grep -i ^Version
rpm -q ray 2>/dev/null
command -v ray >/dev/null && ray --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*ray*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "ray" 2>$null

How to fix CVE-2026-27482

Upgrade ray to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade ray
dpkg -s ray | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh ray -y
# or for older releases:
sudo yum update ray -y
rpm -q ray

SUSE / openSUSE


sudo zypper refresh
sudo zypper update ray
rpm -q ray

Node.js / npm


# Update the affected package in your project
npm install ray@latest
npm ls ray
npm audit fix

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27482 affecting ray
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27482-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*ray*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\ray-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\ray" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "ray" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "ray"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27482 affecting ray
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27482-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s ray 2>/dev/null | grep -i ^Version || echo "ray not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q ray || echo "ray not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27482-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/ray /etc/ray.d /etc/ray.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y ray
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y ray
elif command -v yum >/dev/null; then
    yum update -y ray
elif command -v zypper >/dev/null; then
    zypper --non-interactive update ray
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s ray 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q ray
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27482" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27482"

Disable the affected service (Linux)


sudo systemctl stop ray 2>/dev/null || true
sudo systemctl disable ray 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s ray 2>/dev/null | grep -i ^Version
rpm -q ray 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*ray*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-27482 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27482?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27482?

5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:H.

Where is the official advisory for CVE-2026-27482?

The vendor advisory is at https://github.com/ray-project/ray/security/advisories/GHSA-q5fh-2hc8-f6rq. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27482.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*