Comparison Overview
Lotte Card

Lotte Card
76 Saemunan-ro, Jongno-gu, Seoul, ,, KR
Last Update: 05/10/2026
Lotte Card is a financial service company which provides credit card and lending business in Korea and Vietnam.

Swedbank
Landsvägen 40, SE-172 63, SE, Sundbyberg
Last Update: 18/09/2026
Since 1820, Swedbank has been the bank for the many households and businesses. We are a modern financial services platform focused on customer satisfaction. Our goal is to encourage people to save for a better future, and we aim to help people, businesses and society to...
Compliance Ranges Comparison

Lotte Card







Swedbank






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
Lotte Card has 42.2% fewer 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 Swedbank in 2026.
Incident History - Lotte Card (X = Date, Y = Severity)
Lotte Card cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swedbank (X = Date, Y = Severity)
Swedbank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lotte Card

Swedbank
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.