Comparison Overview
WeTransfer

WeTransfer
Keizersgracht 281, Amsterdam, 1016 ED, NL
Last Update: 16/09/2026
The simplest way to send big files? That’s us. A platform to empower creatives while using business as a force for good? Also us. Our Linked In page is mainly run by our friendly Advertising & Sales team. WeTransfer ads attract the attention of more than 80 million cre...

Baidu, Inc.
Baidu Campus,, Beijing, 100085, CN
Last Update: 14/09/2026
Baidu is a leading AI company with strong Internet foundation, driven by our mission to “make the complicated world simpler through technology”. Founded in 2000 as a search engine platform, we were an early adopter of artificial intelligence in 2010. Since then, we hav...
Compliance Ranges Comparison

WeTransfer







Baidu, Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
WeTransfer 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)
No incidents recorded for Baidu, Inc. in 2026.
Incident History - WeTransfer (X = Date, Y = Severity)
WeTransfer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Baidu, Inc. (X = Date, Y = Severity)
Baidu, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

WeTransfer

Baidu, Inc.
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.