Comparison Overview
Hana Bank

Hana Bank
을지로 35, 중구, 서울시, KR, 04523
Last Update: 06/10/2026
하나은행은 1971년에 설립된 최초 민간 금융기관인 한국투자금융을 모태로 시작하여 2015년 한국외환은행과 합병을 통해 "대한민국 1등 은행"(2015년 6월 기준 국내 은행 자산규모 1위)으로 탄생하였습니다. 또한 국내 은행 최대인 24개국 199개 네트워크를 바탕으로 글로벌 은행으로서의 위치를 견고히 하고 있습니다. "함께 성장하며 행복을 나누는 금융"이라는 미션 아래 금융의 본업(本業)인 사회적 역할 수행을 위해 ESG 경영 및 저탄소 금융을 실천하고 있습니다. 이에 ES...

Aegon
Schiphol Boulevard 223, Schiphol, 1118 BH, NL
Last Update: 01/04/2026
People are living longer, and we are excited about the possibilities this brings. We see longevity, aging, and changing life patterns as an opportunity for our customers, our employees, and society as a whole. And we want to support everyone in building the financial me...
Compliance Ranges Comparison

Hana Bank







Aegon






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
Hana Bank has 14.29% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Aegon in 2026.
Incident History - Hana Bank (X = Date, Y = Severity)
Hana Bank cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aegon (X = Date, Y = Severity)
Aegon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hana Bank

Aegon
FAQ
Latest Global CVEs
A security flaw has been discovered in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b. This affects the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. The manipulation of the argument imgsz/names/kpt_shape results in improper neutralization of directives in dynamically evaluated code. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypass per-IP rate limits on login, one-time passcode, and password validation endpoints, enabling brute-force attacks, and to falsify IP addresses recorded in audit logs.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can submit logins with the password "hunter2" and distinguish HTTP 403 from 401 responses to enumerate valid accounts and reveal the authentication provider of SSO-only users.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a stored HTML injection vulnerability because the ApplicationName and LogoURL appearance settings are rendered into HTML output without sufficient escaping. Attackers with the Owner role can store HTML markup in these settings that renders in the Coder dashboard and in SMTP notification emails sent to other deployment users.
Coder from 2.0.0 before 2.34.8 contains an open redirect vulnerability in handleAPIKeySmuggling that allows attackers to redirect users externally via unsanitized r.URL.Path values. Attackers can craft links on trusted workspace app subdomains with paths beginning with double slashes, which become scheme-relative redirects to attacker sites for phishing.