Comparison Overview
Hanmi Bank

Hanmi Bank
3660 Wilshire Blvd, Los Angeles, 90010, US
Last Update: 31/03/2026
Established in 1982 in Los Angeles, Hanmi Bank was originally founded to serve the underserved immigrant community in Koreatown. From our humble beginnings as the first Korean-American bank, Hanmi Bank has grown to embrace and support the dreams of all Americans. Today,...

Commerzbank AG
Kaiserstraße 16, Frankfurt am Main, 60311, DE
Last Update: 16/09/2026
Commerzbank is the leading bank for the German Mittelstand and a strong partner for around 24,000 corporate client groups. In addition, it supports private and small-business customers in Germany with more than €400 billion assets under management. The Bank’s two Busine...
Compliance Ranges Comparison

Hanmi Bank







Commerzbank AG






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

Hanmi Bank

Commerzbank AG
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.