Comparison Overview
DenizBank

DenizBank
Büyükdere Caddesi 141, Esentepe, 34394, TR
Last Update: 06/09/2026
In 1997, DenizBank was acquired by the Zorlu Holding in the form of a banking license from the Privatization Administration. Undergoing three shareholder changes and done public offering in its short history, the Bank was acquired in October 2006 by Dexia, one of the le...

Abu Dhabi Commercial Bank
Abu Dhabi Commercial Bank Building, Abu Dhabi, 939, AE
Last Update: 01/04/2026
Established in 1985, ADCB places its focus on the UAE where it helps to make a significant contribution to the economy and community it serves. Our aspiration to be the number one bank of choice in the UAE is fueled by the strength and effectiveness of our strategy. Gui...
Compliance Ranges Comparison

DenizBank







Abu Dhabi Commercial Bank






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for DenizBank in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Abu Dhabi Commercial Bank in 2026.
Incident History - DenizBank (X = Date, Y = Severity)
DenizBank cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Abu Dhabi Commercial Bank (X = Date, Y = Severity)
Abu Dhabi Commercial Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DenizBank

Abu Dhabi Commercial Bank
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.