Comparison Overview
Amey

Amey
10 Furnival Street, London, GB, ED4A 1AB
Last Update: 29/03/2026
We are a leading provider of full life-cycle engineering, operations and decarbonisation solutions, for transport infrastructure and complex facilities. Our purpose is delivering sustainable infrastructure, enhancing life, protecting our shared future. We combine excep...

Egis
15 avenue du Centre, Saint-Quentin-en-Yvelines , 78286, FR
Last Update: 02/04/2026
Egis is a leading global architectural, consulting, construction engineering, operations and mobility services firm. We create and operate intelligent infrastructure and buildings that both respond to the climate emergency and contribute to balanced, sustainable and res...
Compliance Ranges Comparison

Amey







Egis






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

Amey

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