Comparison Overview
UniCredit Bank Russia

UniCredit Bank Russia
Prechistenskaya naberezhnaya 9, Moscow, undefined, 119034, RU
Last Update: 28/03/2026
UniCredit Bank is one of the largest banks in Russia and a member of UniCredit, a successful Pan-European Commercial Bank.

Nordea
Aleksanterinkatu 36 B, Helsinki, FI
Last Update: 14/09/2026
We are a universal bank with a 200-year history of supporting and growing the Nordic economies – enabling dreams and aspirations for a greater good. Every day, we work to support our customers’ financial development, delivering best-in-class omnichannel customer experie...
Compliance Ranges Comparison

UniCredit Bank Russia







Nordea






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

UniCredit Bank Russia

Nordea
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.