Comparison Overview
WeTransfer

WeTransfer
Keizersgracht 281, Amsterdam, 1016 ED, NL
Last Update: 15/06/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...

Microsoft
1 Microsoft Way, Redmond, 98052, US
Last Update: 12/08/2026
Every company has a mission. What's ours? To empower every person and every organization to achieve more. We believe technology can and should be a force for good and that meaningful innovation contributes to a brighter world in the future and today. Our culture doesn’t...
Compliance Ranges Comparison

WeTransfer







Microsoft






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for WeTransfer in 2026.
Incidents vs Software Development Industry Avg (This Year)
Microsoft has 1647.57% more incidents than the average of all companies with at least one recorded incident.
Incident History - WeTransfer (X = Date, Y = Severity)
WeTransfer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Microsoft (X = Date, Y = Severity)
Microsoft cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

WeTransfer

Microsoft
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.