Comparison Overview
Microsoft for Healthcare
Microsoft for Healthcare
1 Microsoft Way, Redmond, 98052, US
Last Update: 13/03/2026
At Microsoft and with our health industry partners, we strive to achieve the goal of better health globally; offering people-first solutions to empower organizations, patients, and care providers. Using Microsoft platforms and technologies, Microsoft for Healthcare pro...
Booking.com
Oosterdokskade 163, Amsterdam, 1011 DL, NL
Last Update: 20/04/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
Microsoft for Healthcare
Booking.com
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Microsoft for Healthcare in 2026.
Incidents vs Software Development Industry Avg (This Year)
Booking.com has 266.97% more incidents than the average of all companies with at least one recorded incident.
Incident History - Microsoft for Healthcare (X = Date, Y = Severity)
Microsoft for Healthcare 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
Microsoft for Healthcare
Booking.com
FAQ
Latest Global CVEs
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
A vulnerability was identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable to upgrade the affected component.
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.
A vulnerability was found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.
A vulnerability has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.