Comparison Overview
Grand Millennium Al Seef Basra

Grand Millennium Al Seef Basra
Iraq, Basra, IQ, 61001
Last Update: 04/04/2026
Enjoy the unique experience in the heart of Basra, Iraq, where safety and elegance meet in a 5-star Hotel. Grand Millennium Al Seef Basra, Basra, Iraq is the perfect venue to host your meetings, special events and happy moments with your family and friends. Our Hotel...

Accor
82 rue Henri Farman, Issy-les-Moulineaux, Paris Region, FR, 92130
Last Update: 03/10/2026
We are Accor We are more than 290,000 hospitality experts placing people at the heart of what we do, creating emotion for our guests, and nurturing passion for service and achievement beyond limits. Building on the strength of our teams and of our fully integrated ecos...
Compliance Ranges Comparison

Grand Millennium Al Seef Basra







Accor






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Grand Millennium Al Seef Basra in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Accor in 2026.
Incident History - Grand Millennium Al Seef Basra (X = Date, Y = Severity)
Grand Millennium Al Seef Basra cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Accor (X = Date, Y = Severity)
Accor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Grand Millennium Al Seef Basra

Accor
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.