Comparison Overview
SikaBau AG

SikaBau AG
Reitmenstrasse 7, Schlieren, undefined, 8952, CH
Last Update: 19/03/2026
SikaBau AG ist ein Spezialunternehmen in den Bereichen Bautenschutz, Bauinstandsetzung und Abdichtungen. Wir sind seit 1963 in allen Sprachregionen der Schweiz tätig. Nachhaltige Wertschöpfung ist ein zentraler Faktor für die Zukunftsfähigkeit und den Erfolg von SikaBau...

GMR Group
New Udaan Bhawan, New Delhi, 110037, IN
Last Update: 30/07/2026
GMR Group is a leading Indian infrastructure conglomerate with a diversified presence across Airports, Energy, Transportation, Urban Infrastructure, and Sports. With over two decades of experience, the Group has built world-class assets and pioneered innovations in sust...
Compliance Ranges Comparison

SikaBau AG







GMR Group






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for SikaBau AG in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for GMR Group in 2026.
Incident History - SikaBau AG (X = Date, Y = Severity)
SikaBau AG cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GMR Group (X = Date, Y = Severity)
GMR Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

SikaBau AG

GMR Group
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.