Comparison Overview
Adobe Creative Cloud
Adobe Creative Cloud
345 Park Ave., San Jose, 95110, US
Last Update: 01/04/2026
All the tools you love. Totally re-imagined. Click "Follow" for daily news and inspiration.
Booking.com
Oosterdokskade 163, Amsterdam, 1011 DL, NL
Last Update: 13/09/2026
A career at Booking.com is all about the journey, helping you explore new challenges in a place where you can be your best self. With plenty of exciting twists, turns and opportunities along the way. We’ve always been pioneers, on a mission to shape the future of trav...
Compliance Ranges Comparison
Adobe Creative Cloud
Booking.com
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Adobe Creative Cloud in 2026.
Incidents vs Software Development Industry Avg (This Year)
Booking.com has 296.04% more incidents than the average of all companies with at least one recorded incident.
Incident History - Adobe Creative Cloud (X = Date, Y = Severity)
Adobe Creative Cloud cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Booking.com (X = Date, Y = Severity)
Booking.com cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Adobe Creative Cloud
Booking.com
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.