📄 Description (English)
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.
🤖 AI Executive Summary
Ray AI compute engine versions 2.53.0 and below contain an authentication bypass vulnerability in the dashboard HTTP server that allows unauthenticated DELETE requests via DNS rebinding or same-network attacks. Attackers can shut down Serve instances or delete jobs without user interaction, causing availability disruption. This vulnerability affects organizations using Ray for AI/ML workloads with exposed dashboard interfaces and requires immediate patching to version 2.54.0 or higher.
📄 Description (Arabic)
🤖 AI Intelligence Analysis Analyzed: May 24, 2026 13:55
🇸🇦 Saudi Arabia Impact Assessment
Saudi organizations in AI/ML research, financial services (SAMA-regulated banks using AI for fraud detection), government digital transformation initiatives, and energy sector (ARAMCO's AI operations) are at risk. The vulnerability primarily impacts availability rather than confidentiality. Organizations with Ray dashboards exposed on internal networks or internet-facing without proper network segmentation face drive-by attacks from compromised websites or same-network adversaries. Saudi government entities and critical infrastructure operators using Ray for analytics face operational disruption risks.
🏢 Affected Saudi Sectors
Artificial Intelligence and Machine Learning
Banking and Financial Services
Government and Digital Transformation
Energy and Oil & Gas
Telecommunications
Healthcare and Medical Research
Academic and Research Institutions
🎯 MITRE ATT&CK Techniques
⚖️ Saudi Risk Score (AI)
6.8
/ 10.0
🔧 Remediation Steps (English)
IMMEDIATE ACTIONS:
1. Identify all Ray deployments running versions 2.53.0 or below using asset inventory and vulnerability scanning
2. Restrict dashboard access: Set --dashboard-host to 127.0.0.1 or specific internal IPs instead of 0.0.0.0
3. Implement network segmentation: Place Ray dashboards behind firewalls, VPNs, or internal-only networks
4. Enable authentication: Configure Ray dashboard authentication mechanisms if available
PATCHING:
5. Upgrade Ray to version 2.54.0 or higher immediately across all environments
6. Test upgrades in non-production environments first to ensure compatibility
7. Coordinate patching with dependent applications and services
COMPENSATING CONTROLS (if immediate patching not possible):
8. Implement reverse proxy authentication (nginx/Apache) in front of Ray dashboard
9. Deploy WAF rules to block DELETE requests to Ray dashboard endpoints
10. Monitor for suspicious DELETE requests to Ray API endpoints
DETECTION:
11. Monitor HTTP DELETE requests to Ray dashboard ports (default 8265)
12. Alert on DELETE requests from external or untrusted sources
13. Log all dashboard access attempts and API calls
14. Implement DNS rebinding protection at network perimeter
🔧 خطوات المعالجة (العربية)
الإجراءات الفورية:
1. تحديد جميع نشرات Ray التي تعمل بالإصدارات 2.53.0 وما دونها باستخدام جرد الأصول والفحص الضعيف
2. تقييد وصول لوحة التحكم: اضبط --dashboard-host على 127.0.0.1 أو عناوين IP داخلية محددة بدلاً من 0.0.0.0
3. تنفيذ تقسيم الشبكة: ضع لوحات تحكم Ray خلف جدران الحماية أو الشبكات الافتراضية الخاصة أو الشبكات الداخلية فقط
4. تفعيل المصادقة: قم بتكوين آليات مصادقة لوحة تحكم Ray إن أمكن
التصحيح:
5. ترقية Ray إلى الإصدار 2.54.0 أو أعلى فوراً عبر جميع البيئات
6. اختبار الترقيات في بيئات غير الإنتاج أولاً لضمان التوافق
7. تنسيق التصحيح مع التطبيقات والخدمات التابعة
الضوابط البديلة (إذا لم يكن التصحيح الفوري ممكناً):
8. تنفيذ مصادقة الخادم الوكيل العكسي (nginx/Apache) أمام لوحة تحكم Ray
9. نشر قواعد WAF لحظر طلبات DELETE إلى نقاط نهاية لوحة تحكم Ray
10. مراقبة طلبات DELETE المريبة إلى نقاط نهاية API الخاصة بـ Ray
الكشف:
11. مراقبة طلبات HTTP DELETE إلى منافذ لوحة تحكم Ray (الافتراضي 8265)
12. تنبيه على طلبات DELETE من مصادر خارجية أو غير موثوقة
13. تسجيل جميع محاولات الوصول إلى لوحة التحكم واستدعاءات API
14. تنفيذ حماية DNS rebinding على محيط الشبكة
📋 Regulatory Compliance Mapping
🟢 NCA ECC 2024
5.1.1 - Access Control and Authentication
5.2.1 - Network Security and Segmentation
5.3.1 - Availability and Business Continuity
5.4.1 - Vulnerability Management
🔵 SAMA CSF
ID.AM-2 - Software Inventory
PR.AC-1 - Access Control
PR.PT-2 - Protective Technology
DE.CM-1 - Network Monitoring
RS.MI-2 - Incident Recovery
🟡 ISO 27001:2022
A.5.15 - Access Control
A.5.16 - Authentication
A.6.2 - Network Security
A.8.1 - Asset Management
A.12.6 - Capacity Management
A.14.2 - System Development and Change Management
🔗 References & Sources 4
🔗
https://github.com/ray-project/ray/commit/0fda8b824cdc9dc6edd763bb28dfd7d1cc9b02a4
security-advisories@github.com
Patch
🔗
https://github.com/ray-project/ray/pull/60526
security-advisories@github.com
Issue Tracking
Patch
🔗
https://github.com/ray-project/ray/releases/tag/ray-2.54.0
security-advisories@github.com
Product
Release Notes
🔗
https://github.com/ray-project/ray/security/advisories/GHSA-q5fh-2hc8-f6rq
security-advisories@github.com
Vendor Advisory
Exploit
📦 Affected Products / CPE 1 entries
anyscale:ray