Comparison Overview
Naranja X

Naranja X
La Tablada 451, Córdoba, 5000, AR
Last Update: 20/03/2026
#SomosNaranjaX y nos une algo grande: trabajar por la inclusión y educación financiera de toda la región. Más de 8 millones de personas nos eligen todos los días porque confían en Naranja X para cumplir sus sueños. Somos mucho más que una fintech, con casas distribuid...

Allianz
Koeniginstrasse 28, Munich, 80802, DE
Last Update: 07/10/2026
The Allianz Group is one of the world's leading insurers and asset managers with more than 100 million private and corporate customers in nearly 70 countries. We are proud to be the Worldwide Insurance Partner of the Olympic & Paralympic Movements from 2021 until 2032 a...
Compliance Ranges Comparison

Naranja X







Allianz






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

Naranja X

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