Comparison Overview
Symplectic
Symplectic
6 Briset Street, Barbican, EC1M 5NR, GB
Last Update: 23/12/2025
We work in pursuit of the advancement of knowledge, delivering research management solutions that help universities & funding orgs achieve their research goals. Our software is by used by many of the world’s leading research institutions and our team are known internati...
Rakuten
Rakuten Crimson House, Setagaya-ku, 158-0094, JP
Last Update: 10/09/2026
Rakuten Group, Inc. (TSE: 4755) is a global technology leader in services that empower individuals, communities, businesses and society. Founded in Tokyo in 1997 as an online marketplace, Rakuten has expanded to offer services in e-commerce, fintech, digital content and...
Compliance Ranges Comparison
Symplectic
Rakuten
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Symplectic in 2026.
Incidents vs Software Development Industry Avg (This Year)
Rakuten has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Symplectic (X = Date, Y = Severity)
Symplectic cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Rakuten (X = Date, Y = Severity)
Rakuten cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Symplectic
Rakuten
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.