Comparison Overview
PariPassu
PariPassu
Worldwide, US
Last Update: 13/03/2026
At PariPassu, we’re building the world’s most powerful network of founder support—where capital is supercharged by community. One deal at a time, we’re building a faster, more flexible way for founders, operators, and accredited tech enthusiasts to co-invest in industr...
Essar
Essar House, 11, Keshavrao Khadye Marg, Mahalaxmi, Mumbai, 400 034, IN
Last Update: 14/09/2026
Essar, with an entrepreneurial track record spanning 50+ years, specialises in investing and developing assets to create value in core sectors such as Energy, Infrastructure, Metals & Mining, and Technology & Retail. With a presence in eight countries, Essar generates r...
Compliance Ranges Comparison
PariPassu
Essar
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for PariPassu in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Essar in 2026.
Incident History - PariPassu (X = Date, Y = Severity)
PariPassu cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Essar (X = Date, Y = Severity)
Essar cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PariPassu
Essar
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.