Comparison Overview
KU Leuven Research & Development

KU Leuven Research & Development
Waaistraat 6, 3000 Leuven, Leuven, 3000, BE
Last Update: 03/02/2026
KU Leuven Research & Development (LRD) supports scientists who want to transform their research into impactful innovations. As the KU Leuven Association’s technology transfer office, we guide them in putting their research results at the service of society, economy and ...

Technical University of Munich
Arcisstraße 21, München, Munich, Bavaria, DE, 80333
Last Update: 02/04/2026
Our university combines top-class facilities for cutting-edge research with unique learning opportunities for 52,000 students. Whether our researchers are investigating the origins of life, matter and the universe or looking for solutions to the major challenges for our...
Compliance Ranges Comparison

KU Leuven Research & Development







Technical University of Munich






Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for KU Leuven Research & Development in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Technical University of Munich in 2026.
Incident History - KU Leuven Research & Development (X = Date, Y = Severity)
KU Leuven Research & Development cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Technical University of Munich (X = Date, Y = Severity)
Technical University of Munich cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

KU Leuven Research & Development

Technical University of Munich
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.