Comparison Overview
QNB Sigorta

QNB Sigorta
Kardelen Sokak, None, Atasehir, Istanbul, TR, 34746
Last Update: 07/03/2026
QNB Sigorta olarak bireysel emeklilik, sağlık, hayat ve ferdi kaza sigortası branşlarında güvende ve iyi hissettiren sigortacılık anlayışıyla müşterilerimizle buluşuyoruz. Türkiye’nin en büyük özel bankalarından biri olan QNB'nin iştiraki olarak, köklü deneyimimizden al...

Mapfre
Carretera de Pozuelo, 52, Majadahonda, Community of Madrid, ES, 28220
Last Update: 03/09/2026
At Mapfre, we’ve spent more than 90 years supporting people and businesses around the world, taking care of what matters most to them. We offer insurance, financial, and service solutions that evolve with you. Our experience and commitment, combined with a constant focu...
Compliance Ranges Comparison

QNB Sigorta







Mapfre






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

QNB Sigorta

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