Comparison Overview
Otokoç Otomotiv

Otokoç Otomotiv
Aydınevler Mah. Saygı Cad. No:60/1, İstanbul, Küçükyalı, 34854, TR
Last Update: 11/03/2026
Koç Topluluğu’nun kurucusu merhum Vehbi Koç tarafından, 1928 yılında Ankara’da “Ford Motor Company” acenteliğinin alınmasıyla kurulan Koç Holding’in ilk otomotiv sektörü yatırımı olan Otokoç Otomotiv’in temelleri atılmıştır. Otomotivle ilgili tüm çözümleri tek çatı alt...

Costa Coffee
1A Wimpole St, London, W1G 0EA, GB
Last Update: 13/09/2026
At Costa Coffee, we’ve been crafting with heart and changing the coffee game since 1971. Now part of The Coca-Cola Company, we proudly operate in over 50 countries, and we’re still growing! And we’re much more than our beloved stores. Consumers all over the world can no...
Compliance Ranges Comparison

Otokoç Otomotiv







Costa Coffee






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

Otokoç Otomotiv

Costa Coffee
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.