Comparison Overview
Pegasus
Pegasus
370 Lexington Ave, New York, New York, 10017, US
Last Update: 29/03/2026
Pegasus has recently merged with Cendyn, bringing together two of the leading technology providers in the hospitality industry, helping us deliver on our mission of personalizing and enriching the guest journey. For more information, please visit Cendyn's LinkedIn page.
Landry's
1510 West Loop South, Houston, 77027, US
Last Update: 13/09/2026
Landry's is a multinational, diversified restaurant, hospitality, gaming, and entertainment leader based in Houston, Texas. The company operates more than 600 establishments around the world, including well-known concepts, such as Landry’s Seafood House, Bubba Gump S...
Compliance Ranges Comparison
Pegasus
Landry's
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Pegasus in 2026.
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Landry's in 2026.
Incident History - Pegasus (X = Date, Y = Severity)
Pegasus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Landry's (X = Date, Y = Severity)
Landry's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pegasus
Landry's
FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.