Comparison Overview
Nations Trust Bank Private Banking

Nations Trust Bank Private Banking
242, Union Place , Colombo 02, undefined, 00200, LK
Last Update: 15/05/2026
Welcome to Nations Trust Bank Private Banking, a financial solution created to satisfy the financial needs of your lifestyle. Focusing on three main criteria of wealth management, lifestyle and the next generation, we provide an unparalleled array of products and servic...

LCL
20, Avenue de Paris, VILLEJUIF, Île-de-France, FR, 94800
Last Update: 14/09/2026
Depuis son rapprochement avec le Groupe Crédit Agricole SA en 2003, le périmètre d'activités de LCL, réseau national de banque de détail, est axé sur le marché des particuliers, des professionnels, des entreprises et la Banque privée. LCL est une banque de proximité ...
Compliance Ranges Comparison

Nations Trust Bank Private Banking







LCL






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

Nations Trust Bank Private Banking

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