Comparison Overview
SEB

SEB
Kungsträdgårdsgatan 8, Stockholm, 10640, SE
Last Update: 10/09/2026
SEB is a leading northern European financial services group with a strong belief that entrepreneurial minds and innovative companies are key in creating a better world. SEB takes a long-term perspective and supports its customers in good times and bad. In Sweden and ...

Sberbank
RU
Last Update: 05/04/2026
Сбер — крупнейший банк в России, поставщик надёжных технологических решений и один из ведущих финансовых институтов страны. Мы не боимся меняться и открывать новые горизонты, но в то же время остаёмся верными принципам, сформированным за нашу 180-летнюю историю. Такой п...
Compliance Ranges Comparison

SEB







Sberbank






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

SEB

Sberbank
FAQ
Latest Global CVEs
Use after free in Microsoft Edge (Chromium-based) allows an unauthorized attacker to elevate privileges over a network.
Heap-based buffer overflow in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
A flaw was found in Podman. If an attacker can pass a crafted tar archive to the `podman load` command, they can create files on the host machine with the privileges of the user running Podman.
Integer overflow or wraparound vulnerability in Samsung Opensource Escargot allows attackers with write access to the bytecode-cache directory to cause a heap-based buffer overflow and denial of service via a crafted cache file. This issue affects Escargot: ac94df78493ee6fede286620d94f724e46b4d238.
Netcore NR255-V version 1.5.130703 contains a stored cross-site scripting vulnerability in L7 content management pages that use eval() sinks, affecting the call board text and policy group handling components. Attackers can inject persistent script payloads through these pages to have malicious code executed in the context of other users viewing the affected content.