Comparison Overview
Pullman Hotels & Resorts

Pullman Hotels & Resorts
82, Rue Henry Farman, Issy-les-Moulineaux, Ile-de-France, 92130, FR
Last Update: 01/11/2025
Pullman Hotels & Resorts sets a new tempo in global travel and living, delivering an inspiring, energizing and enriching experience to new entrepreneurs. Pullman welcomes guests with the space they need to focus, work and play. Forward-thinking, hyper-connected and with...

Hilton
7930 Jones Branch Drive, McLean, 22102, US
Last Update: 26/09/2026
Hilton (NYSE: HLT) is a leading global hospitality company with a portfolio of 27 world-class brands comprising more than 9,100 properties and over 1.3 million rooms, in 143 countries and territories. Dedicated to fulfilling its founding vision to fill the earth with th...
Compliance Ranges Comparison

Pullman Hotels & Resorts







Hilton






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

Pullman Hotels & Resorts

Hilton
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)