Comparison Overview
Ipoteka bank OTP Group

Ipoteka bank OTP Group
Shahrisabz 30, Tashkent, Mirzo Ulugbek, UZ, 100000
Last Update: 18/12/2025
JSCMB Ipoteka bank OTP Group is the fifth largest bank in the banking system of Uzbekistan. The Bank accounts almost 7% of total assets and deposits in the banking system The bank serves more than 1.8 million corporate and retail clients through 39 branches and 212 cus...

Citizens
1 Citizens Plaza, Providence, 02903, US
Last Update: 22/04/2026
At Citizens, we recognize that the journey to accomplishment is no longer linear and that individuals are made of all they have done and all they are going to do. As one of the oldest and largest financial services firms in the United States with a history dating back t...
Compliance Ranges Comparison

Ipoteka bank OTP Group







Citizens






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Ipoteka bank OTP Group in 2026.
Incidents vs Banking Industry Avg (This Year)
Citizens has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Ipoteka bank OTP Group (X = Date, Y = Severity)
Ipoteka bank OTP Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Citizens (X = Date, Y = Severity)
Citizens cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ipoteka bank OTP Group

Citizens
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.