Comparison Overview
Club21

Club21
COMO House, 6B Orange Grove Road, Singapore, SG, 258332
Last Update: 02/04/2026
Founded in 1972 as a multi-label store in Tanglin Shopping Centre, Singapore, Club21 is one of Asia’s leading purveyors of luxury fashion. With an established e-commerce platform and a network of nearly 150 stores spanning Singapore, Malaysia, Taiwan and Thailand, we ...

MANGO
Mercaders 9-11, Palau Solità i Plegamans, 08184, ES
Last Update: 09/09/2026
Mango, one of the leading international fashion groups, is a global company with design and creativity at the heart of its business model and a strategy based on constant innovation, the pursuit of sustainability and a complete ecosystem of channels and partners. With ...
Compliance Ranges Comparison

Club21







MANGO






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

Club21

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