Comparison Overview
Atkins

Atkins
Ashley Road, Epsom, KT18 5BW, GB
Last Update: 01/04/2026
Atkins is now AtkinsRéalis. Please follow AtkinsRéalis on LinkedIn. We are a world-class engineering services and nuclear organization. We connect people, data and technology to transform the world’s infrastructure and energy systems. Together, with our industry part...

Capgemini Engineering
76, Avenue Kléber, Paris, Île-de-France, FR, 75116
Last Update: 01/04/2026
World leader in engineering and R&D services, Capgemini Engineering combines its broad industry knowledge and cutting-edge technologies in digital and software to support the convergence of the physical and digital worlds. Coupled with the capabilities of the rest of th...
Compliance Ranges Comparison

Atkins







Capgemini Engineering






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

Atkins

Capgemini Engineering
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.