Comparison Overview
PayPal
PayPal
2211 North First Street, San Jose, 95131, US
Last Update: 09/09/2026
We're championing possibilities for all by making money fast, easy, and more enjoyable. Our hope is to unlock opportunities for people in their everyday lives and empower the millions of people and businesses around the world who trust, rely, and use PayPal every day. ...
Shopee
5 Science Park Dr, Shopee Building, Singapore, 118265, SG
Last Update: 09/09/2026
Shopee is a leading e-commerce platform in Southeast Asia, Taiwan, and Brazil. Launched in 2015, our platform connects shoppers, brands and sellers within one ecosystem. Shopee offers an easy, secure and engaging online shopping experience enjoyed by millions of people...
Compliance Ranges Comparison
PayPal
Shopee
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
PayPal has 554.21% more 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 Shopee in 2026.
Incident History - PayPal (X = Date, Y = Severity)
PayPal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Shopee (X = Date, Y = Severity)
Shopee cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PayPal
Shopee
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.