Comparison Overview
Rolls-Royce India

Rolls-Royce India
2nd Floor, Birla Tower (West), New Delhi, undefined, undefined, IN
Last Update: 20/11/2025
Rolls-Royce shares a rich legacy of partnership with India that spans 90 years. We have a strong presence in the country across all businesses - Defence, Civil Aviation and Power Systems. Today, we are well-positioned in this region with an ecosystem of strategic partne...

SKF Group
Sven Wingquist Gata 2, Göteborg, SE-415 50, SE
Last Update: 01/04/2026
We fight friction to move the world forward. 20% of all energy consumed is spent overcoming friction. At SKF, we’re constantly fighting that friction, to reduce energy waste and make the most of the resources we have. Since 1907, we’ve been making some of the world’...
Compliance Ranges Comparison

Rolls-Royce India







SKF Group






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Rolls-Royce India in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for SKF Group in 2026.
Incident History - Rolls-Royce India (X = Date, Y = Severity)
Rolls-Royce India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SKF Group (X = Date, Y = Severity)
SKF Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Rolls-Royce India

SKF Group
FAQ
Latest Global CVEs
vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, the fix for CVE-2026-22778, which introduced a sanitize_message helper that strips object-repr memory addresses from error messages before they reach the client, is incomplete: several response paths echo str(exc) directly to clients without calling sanitize_message. The unsanitized sites include the Anthropic API router in vllm/entrypoints/anthropic/api_router.py (the POST /v1/messages and POST /v1/messages/count_tokens handlers), the Server-Sent Events streaming converter in vllm/entrypoints/anthropic/serving.py, and the realtime speech-to-text WebSocket in vllm/entrypoints/speech_to_text/realtime/connection.py. These paths catch the exception inside the route coroutine and construct the JSONResponse themselves, bypassing the sanitizing global FastAPI exception handler, and WebSocket frames do not traverse that handler chain at all. Using the same primitive as the parent issue, an unauthenticated attacker can send malformed image bytes through the Anthropic Messages API image content parts so that PIL.Image.open raises an UnidentifiedImageError whose message contains the BytesIO object repr, leaking the heap memory address verbatim in the error.message field of the response body. This vulnerability is fixed in 0.23.1rc0.
vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, ll temperature validation gates use comparison operators (<, >), which silently evaluate to False for NaN and for positive Infinity in Python's IEEE 754 float semantics. Both values pass every guard and propagate to GPU sampling kernels, where they produce undefined behavior or CUDA errors that can crash the inference worker. This vulnerability is fixed in 0.23.1rc0.
vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.23.1rc0, vLLM's /v1/audio/transcriptions endpoint limits compressed upload size but not decoded PCM output. A 25MB OPUS file expands to ~14.9GB of float32 PCM at decode time. This vulnerability is fixed in 0.23.1rc0.
vLLM is an inference and serving engine for large language models (LLMs). Prior to 0.22.1, the vLLM Dockerfile is vulnerable to a dependency confusion attack through the flashinfer-jit-cache package. The package is installed from a custom index (flashinfer.ai/whl/) using --extra-index-url, but the package name was not registered on PyPI, and UV_INDEX_STRATEGY="unsafe-best-match" is set globally. An attacker who registers flashinfer-jit-cache on PyPI with version 0.6.11.post2 can execute arbitrary code as root during the Docker build and backdoor every resulting container image, enabling exfiltration of all user prompts, API credentials, and model data from production vLLM deployments This vulnerability is fixed in 0.22.1.
vLLM is an inference and serving engine for large language models (LLMs). From 0.5.5 until 0.23.1rc0, integer truncation of tensor dimensions in vLLM's GGUF dequantize kernels (csrc/quantization/gguf/gguf_kernel.cu) causes partial tensor processing. The output tensor is allocated at full size via torch::empty (uninitialized memory), but the dequantize CUDA kernel processes only a truncated number of elements. The unfilled portion of the output tensor retains whatever was previously in GPU memory. In multi-tenant inference deployments, this residual GPU memory may contain tensor data from other users' inference requests, constituting information disclosure. This vulnerability is fixed in 0.23.1rc0.