Comparison Overview
Spreadconnect

Spreadconnect
Gießerstraße 27, Leipzig, Saxony, DE
Last Update: 02/04/2026
Spreadconnect lets you sell high-quality products on any channel without having stock risks, production facilities or fulfillment knowledge. Born from the European market leader Spreadshirt, Spreadconnect’s roots are deeply planted in over 20 years of print-on-demand ex...

Sohu.com
Vision international Centre,No.1 Park Zhongguancun East Road,Haidian District,, Beijing, 100084, CN
Last Update: 03/04/2026
Sohu.com Inc. (NASDAQ: SOHU) is China's premier online brand and indispensable to the daily life of millions of Chinese, providing a network of web properties and community based/web 2.0 products which offer the vast Sohu user community a broad array of choices regardin...
Compliance Ranges Comparison

Spreadconnect







Sohu.com






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Spreadconnect in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Sohu.com in 2026.
Incident History - Spreadconnect (X = Date, Y = Severity)
Spreadconnect cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sohu.com (X = Date, Y = Severity)
Sohu.com cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Spreadconnect

Sohu.com
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.