Comparison Overview
Privalia

Privalia
Avenida Professor Alceu Maynard Araújo, 698, São Paulo, SP, BR, 04726-160
Last Update: 11/03/2026
Oi, somos a Privalia =) A plataforma que, todos os dias, traz oportunidades incríveis das marcas que você mais ama. Queremos surpreender. Conectar pessoas com as histórias que elas querem viver. Somos uma empresa movida pelo desafio de transformar o mercado de e-comme...

Under Armour
101 Performance Dr, Baltimore, 21230, US
Last Update: 11/09/2026
Our Belief: WE USE THE POWER OF SPORTS TO EXPAND EVERY PLAYING FIELD. Our Obsession: WE ARE OBSESSED WITH ATHLETES WHO STRIVE FOR MORE – IN SPORTS, IN LIFE, AND IN THE WORLD. Our Mission: TO INSPIRE ATHLETES WITH INNOVATIVE PERFORMANCE AND DESIGN SOLUTIONS THEY CAN’T LI...
Compliance Ranges Comparison

Privalia







Under Armour






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

Privalia

Under Armour
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.