Comparison Overview
Rolls-Royce

Rolls-Royce
90 York Way, London, N1 9FX, GB
Last Update: 22/03/2026
At Rolls-Royce, we're a force for progress: powering, protecting and connecting people everywhere. We’ve been at the forefront of innovation for more than a hundred years. Our engineering excellence is the power behind some of the most critical technologies used in the...

TK Elevator
E-Plus Straße 1, Düsseldorf, North Rhine-Westphalia, DE, 40472
Last Update: 01/04/2026
𝗪𝗲𝗹𝗰𝗼𝗺𝗲 𝘁𝗼 𝗧𝗞 𝗘𝗹𝗲𝘃𝗮𝘁𝗼𝗿 – 𝗪𝗵𝗲𝗿𝗲 𝗜𝗻𝗴𝗲𝗻𝘂𝗶𝘁𝘆 𝗘𝗹𝗲𝘃𝗮𝘁𝗲𝘀 𝗨𝗿𝗯𝗮𝗻 𝗟𝗶𝘃𝗶𝗻𝗴 Engineering pioneer. Global industry leader. TK Elevator draws on a legacy of firsts – from a groundbreaking vertical conveyor in 1890 – to evolve modern ...
Compliance Ranges Comparison

Rolls-Royce







TK Elevator






Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
Rolls-Royce has 0.0% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for TK Elevator in 2026.
Incident History - Rolls-Royce (X = Date, Y = Severity)
Rolls-Royce cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TK Elevator (X = Date, Y = Severity)
TK Elevator cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Rolls-Royce

TK Elevator
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.