Comparison Overview
OEC

OEC
3600 Embassy Pkwy, Fairlawn, Ohio, US, 44333
Last Update: 09/06/2026
Playing our part right from the start. Back in 2000, OEMs were facing a huge hurdle selling parts into dealerships, mechanical shops, and collision shops. Every transaction was handled manually, either by phone or fax, which left the market desperate for a faster, more...

Agoda
20 Cecil Street, #1401, Singapore, 049705, SG
Last Update: 13/09/2026
At Agoda, we bridge the world through travel. We aim to make it easy and rewarding for more travelers to explore and experience the amazing world we live in. We do so by enabling more people to see the world for less – with our best-value deals across our 6,000,000+ hot...
Compliance Ranges Comparison

OEC







Agoda






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
OEC has 4.76% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
Agoda has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - OEC (X = Date, Y = Severity)
OEC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Agoda (X = Date, Y = Severity)
Agoda cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OEC

Agoda
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.