Comparison Overview
ArcelorMittal Ostrava

ArcelorMittal Ostrava
Vratimovská 689, Ostrava-Kunčice, undefined, 702 02, CZ
Last Update: 19/12/2025
Říká se, že vše kolem nás je buďto z oceli, nebo bylo vyrobeno ocelovým přístrojem. A není to nadsázka - ocel je skutečně nejdůležitějším materiálem v našich životech. Provází nás každý den a život bez ní si lze jen těžko představit. Ocel je šetrná k přírodě, protože je...

Alcoa
201 Isabella St., Suite 500, Pittsburgh, PA, US, 15212
Last Update: 04/04/2026
Recruitment Fraud Alert: Alcoa has become aware of some fraudulent employment offers being sent to candidates via social media channels. Alcoa never makes job offers or asks for bank details through social media. Always verify the authenticity of any recruitment communi...
Compliance Ranges Comparison

ArcelorMittal Ostrava







Alcoa






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

ArcelorMittal Ostrava

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