Comparison Overview
Salle Gustave Eiffel

Salle Gustave Eiffel
N/A
Last Update: 31/03/2026
Organisez vos événements au sein d’un des plus beaux monuments au monde, un rêve réalisable dans la Salle Gustave Eiffel. Située au 1er étage de la Tour Eiffel, elle se propose à la privatisation B2B. C’est l’occasion de faire de vos événements des moments inoubliables ...

BCD Travel
Europalaan 300, Utrecht, NL, 3526 KS
Last Update: 15/10/2026
BCD Travel helps companies travel smart and achieve more. We drive program adoption, cost savings and talent retention through digital experiences that simplify business travel. Our 15,000+ dedicated team members service clients in 170+ countries as we shape a sustainab...
Compliance Ranges Comparison

Salle Gustave Eiffel







BCD Travel






Benchmark & Cyber Underwriting Signals
Incidents vs Travel Arrangements Industry Avg (This Year)
No incidents recorded for Salle Gustave Eiffel in 2026.
Incidents vs Travel Arrangements Industry Avg (This Year)
BCD Travel has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Salle Gustave Eiffel (X = Date, Y = Severity)
Salle Gustave Eiffel cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BCD Travel (X = Date, Y = Severity)
BCD Travel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Salle Gustave Eiffel

BCD Travel
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.