Comparison Overview
Zagrebačka banka

Zagrebačka banka
Trg bana Josipa Jelačića 10, Zagreb, 10 000, HR
Last Update: 25/11/2025
Osnažujemo razvoj zajednice. Svrha je UniCreditova postojanja osnažiti zajednice kako bi mogle napredovati, ispuniti očekivanja svih naših dionika u cijeloj Europi i osloboditi potencijal svakog pojedinca kojem smo na usluzi, kao i svake zajednice. UniCredit je pane...

alinma
King Fahad Road - Alanoud Northern Tower, PO Box 66674, Riyadh, SA, 11586
Last Update: 02/04/2026
Alinma Bank is a Saudi joint stock company formed in accordance with Royal Decree No. M/15 dated 28/2/1427H (28/3/2006) and Ministerial Resolution No. 42 dated 27/2/1427H (27/3/2006). The share capital of Alinma Bank is SAR 20 billion consisting of 1.5 billion shares wi...
Compliance Ranges Comparison

Zagrebačka banka







alinma






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Zagrebačka banka in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for alinma in 2026.
Incident History - Zagrebačka banka (X = Date, Y = Severity)
Zagrebačka banka cyber incidents detection timeline including parent company and subsidiaries.
Incident History - alinma (X = Date, Y = Severity)
alinma cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Zagrebačka banka

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