Comparison Overview
ReachCentrum

ReachCentrum
Cantersteen 47, Brussels, 1000, BE
Last Update: 05/12/2025
ReachCentrum is the professional services body established originally by Cefic, the European Chemical Industry Council and since May 2015 part of ERM, the world’s leading sustainability consultancy. At ReachCentrum we provide guidance to get acquainted with the REACH re...

Givaudan
Givaudan International SA, Vernier, 1214, CH
Last Update: 01/04/2026
Givaudan is a global leader in Fragrance & Beauty and Taste & Wellbeing. We celebrate the beauty of human experience by creating for happier, healthier lives with love for nature. Together with our customers we deliver food experiences, craft inspired fragrances, and de...
Compliance Ranges Comparison

ReachCentrum







Givaudan






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

ReachCentrum

Givaudan
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.