Comparison Overview
Fairmont The Queen Elizabeth

Fairmont The Queen Elizabeth
900, René-Levesque West, Montreal, Quebec, CA, H3B 4A5
Last Update: 19/01/2026
Fairmont Le Reine Elizabeth a rouvert ses portes après une transformation complète de 140 millions de dollars, investis par Ivanhoé Cambridge afin de transformer l’expérience hôtelière et devenir la destination par excellence des Montréalais et hôtel de premier choix po...

J D Wetherspoon
Central Park, Watford, WD24 4QL, GB
Last Update: 06/09/2026
J D Wetherspoon is a leading pub operator in the UK and Ireland. Back in 1979, founder chairman Tim Martin opened the very first Wetherspoon – in Muswell Hill, north London. Today, Tim and the company run over 850 pubs and hotels, spread right across the UK and, more re...
Compliance Ranges Comparison

Fairmont The Queen Elizabeth







J D Wetherspoon






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Fairmont The Queen Elizabeth in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for J D Wetherspoon in 2026.
Incident History - Fairmont The Queen Elizabeth (X = Date, Y = Severity)
Fairmont The Queen Elizabeth cyber incidents detection timeline including parent company and subsidiaries.
Incident History - J D Wetherspoon (X = Date, Y = Severity)
J D Wetherspoon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Fairmont The Queen Elizabeth

J D Wetherspoon
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.