Comparison Overview
Peatix

Peatix
413 W 14th St, New York, 10014, US
Last Update: 01/04/2026
Peatix is an event discovery platform that connects people to communities through a shared passion for all things similar and different. Whether you are an aspiring home cook looking for live stream classes from the comforts of your own kitchen, a music junkie looking t...

Sohu.com
Vision international Centre,No.1 Park Zhongguancun East Road,Haidian District,, Beijing, 100084, CN
Last Update: 12/09/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

Peatix







Sohu.com






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Peatix in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Sohu.com in 2026.
Incident History - Peatix (X = Date, Y = Severity)
Peatix 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

Peatix

Sohu.com
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.