Comparison Overview
QNB Finansleasing

QNB Finansleasing
Esentepe Mah. Büyükdere Cad. Kristal Kule Binası, İstanbul, undefined, 34394, TR
Last Update: 26/04/2026
Ülkemizde leasing sektörünün ilk kurulan şirketlerinden biri olan QNB Leasing , 1990 yılından beri yatırımların finansmanında aktif rol oynamaktadır. Kuruluşundan itibaren lider firma olmayı hedefleyen Şirket bu hedefini gerçekleştirmek için herzaman müşteri odaklı stra...

Fifth Third Bank
38 Fountain Square Plaza, Cincinnati, 45202, US
Last Update: 05/09/2026
At Fifth Third Bank, everything we do is rooted in our purpose: to improve the lives of our customers and the well-being of our communities. Since our founding in 1858, we’ve been committed to creating a better financial experience by empowering our customers and client...
Compliance Ranges Comparison

QNB Finansleasing







Fifth Third Bank






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for QNB Finansleasing in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Fifth Third Bank in 2026.
Incident History - QNB Finansleasing (X = Date, Y = Severity)
QNB Finansleasing cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fifth Third Bank (X = Date, Y = Severity)
Fifth Third Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

QNB Finansleasing

Fifth Third Bank
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.