Comparison Overview
SEB Latvija

SEB Latvija
Meistaru iela 1, Valdlauci, Kekavas pagasts, Kekavas novads, LV 1010, LV
Last Update: 23/04/2026
Nākotne nebūs tāda, kādu mēs to iztēlojamies – tā būs labāka. Jauni piedzīvojumi un labāki lēmumi. Sazinies ar mums, kad nonāc pie dzīves lielajiem lēmumiem: www.seb.lv

Lloyds Banking Group
25 Gresham Street, London, EC2V 7HN, GB
Last Update: 04/04/2026
Our purpose is Helping Britain Prosper. We do this by creating a more sustainable and inclusive future for people and businesses, shaping finance as a force for good. We're part of an ever-changing industry and are currently on a journey to shape the financial services...
Compliance Ranges Comparison

SEB Latvija







Lloyds Banking Group






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

SEB Latvija

Lloyds Banking Group
FAQ
Latest Global CVEs
A vulnerability was identified in ealpha072 Student-Management-System up to 01451bd7a2f58cdda07bd0b86e3967582e3ecd08. Affected by this issue is some unknown functionality of the file admin/config.php of the component Administrative Backend. Such manipulation leads to improper authentication. The attack may be performed from remote. The exploit is publicly available and might be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was determined in sgl-project SGLang up to 0.5.11. Affected by this vulnerability is the function data_hash of the component Cache Handler. This manipulation causes denial of service. The attack is restricted to local execution. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
Active IQ Config Advisor version 6.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
A vulnerability was found in crmeb crmeb_java 1.4. Affected is the function RestTemplate.getForEntity of the file crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java of the component base64 Qrcode Endpoint. The manipulation of the argument url results in server-side request forgery. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.