Comparison Overview
Scientific Beta
Scientific Beta
2 Shenton Way, Singapore, undefined, 068804, SG
Last Update: 03/03/2026
Scientific Beta aims to be the first provider of a smart factor and ESG/climate index platform to help investors understand and invest in advanced factor and ESG/climate equity strategies. Established by EDHEC-Risk Institute, one of the top academic institutions in the ...
MassMutual
1295 State Street, Springfield, 01111, US
Last Update: 12/09/2026
Living mutual has always been at the core of our human existence, and it's the principle that's guided us since our founding in 1851. It's not a concept we invented, but one we champion for the simple reason that people take it for granted today. While the world would ...
Compliance Ranges Comparison
Scientific Beta
MassMutual
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Scientific Beta in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for MassMutual in 2026.
Incident History - Scientific Beta (X = Date, Y = Severity)
Scientific Beta cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MassMutual (X = Date, Y = Severity)
MassMutual cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Scientific Beta
MassMutual
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.