Comparison Overview
Eiffage Métal

Eiffage Métal
3, Place de l'europe, Vélizy-Villacoublay, Île-de-France 78140, FR
Last Update: 23/02/2026
Eiffage Métal : défier la complexité Eiffage Métal est dédiée à la construction métallique clés en main. Ses équipes conçoivent et réalisent des enveloppes et façades de bâtiments et des ouvrages d’art. Spécialisée dans les projets complexes multitechniques, elle est é...

International Brotherhood of Electrical Workers (IBEW)
900 7th Street, NW, Washington, 20001, US
Last Update: 02/04/2026
The IBEW represents 860,000 active. and retired who work in a wide variety of fields, including utilities, construction, telecommunications, broadcasting, manufacturing, railroads and government. The IBEW has members in both the United States and Canada and stands out ...
Compliance Ranges Comparison

Eiffage Métal







International Brotherhood of Electrical Workers (IBEW)






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Eiffage Métal in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for International Brotherhood of Electrical Workers (IBEW) in 2026.
Incident History - Eiffage Métal (X = Date, Y = Severity)
Eiffage Métal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Brotherhood of Electrical Workers (IBEW) (X = Date, Y = Severity)
International Brotherhood of Electrical Workers (IBEW) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Eiffage Métal

International Brotherhood of Electrical Workers (IBEW)
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.