Comparison Overview
Louis Berger

Louis Berger
412 Mount Kemble Ave, Morristown, New Jersey, 07960, US
Last Update: 03/04/2026
Louis Berger was acquired by WSP. This channel is no longer active. For updates, please follow WSP. Louis Berger is a global professional services corporation that helps infrastructure and development clients solve their most complex challenges. We are a trusted partn...

Fugro
Veurse Achterweg 10, Leidschendam, 2264 SG, NL
Last Update: 01/04/2026
We are the world’s leading Geo-data specialist, collecting and analysing comprehensive information about the Earth and the structures built upon it. Through integrated data acquisition, analysis and advice, we unlock insights from Geo-data to help our clients design, bu...
Compliance Ranges Comparison

Louis Berger







Fugro






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

Louis Berger

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