Comparison Overview
UNIQLO

UNIQLO
UNIQLO CITY TOKYO, 1-6-7 Ariake,Koto-ku, Tokyo, JP
Last Update: 08/09/2026
About UNIQLO LifeWear Apparel that comes from the Japanese values of simplicity, quality, and longevity. Designed to be of the time and for the time, LifeWear is made with such modern elegance that it becomes the building blocks of each individual’s style. A perfect shi...

Titan Company Limited
#193, Veerasandra,, Electronic City, Bangalore , 560100, IN
Last Update: 14/09/2026
Titan Company Ltd is the organization that brought about a paradigm shift in the Indian watch market when it introduced its futuristic quartz technology, complemented by international styling. With India's two most recognized and loved brands Titan and Tanishq to its cr...
Compliance Ranges Comparison

UNIQLO







Titan Company Limited






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

UNIQLO

Titan Company Limited
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.