Comparison Overview
Wolfgang Puck Catering

Wolfgang Puck Catering
8687 Melrose Avenue, West Hollywood, CA, 90069, US
Last Update: 19/02/2026
At Wolfgang Puck Catering, we are dedicated to sharing our passion for culinary innovation, uncompromising quality and genuine hospitality with our clients and guests. Trust our team of expert chefs and planners to deliver a restaurant quality experience for your next ...

Kempinski Hotels
Maximilianstrasse 17, Munich, 80539, DE
Last Update: 13/09/2026
Founded in Germany in 1897, Kempinski Hotels has long reflected the finest traditions of European hospitality. Today, as ever, Kempinski is synonymous with distinctive luxury. Located in many of the world's most well-known cities and resorts, the Kempinski collection i...
Compliance Ranges Comparison

Wolfgang Puck Catering







Kempinski Hotels






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Wolfgang Puck Catering in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Kempinski Hotels in 2026.
Incident History - Wolfgang Puck Catering (X = Date, Y = Severity)
Wolfgang Puck Catering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kempinski Hotels (X = Date, Y = Severity)
Kempinski Hotels cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Wolfgang Puck Catering

Kempinski Hotels
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.