Comparison Overview
Vinland Capital
Vinland Capital
Rua Amauri 255, São Paulo, SP, 01448-000, BR
Last Update: 03/02/2026
Our edge is to create alpha by investing in global to local themes. Vinland’s objective is to apply macro and equity strategies to generate high risk adjusted returns for investors seeking opportunities across different asset classes globally, with a deep focus in Lati...
Sonae
Maia, Porto, 4470-177, PT
Last Update: 15/09/2026
Sonae exists to create a lasting positive impact on businesses, people, communities and on the planet. Managing a diverse portfolio of businesses in retail, financial services, technology, investments, real estate and telecommunications, Sonae makes the most of its ex...
Compliance Ranges Comparison
Vinland Capital
Sonae
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Vinland Capital in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Sonae in 2026.
Incident History - Vinland Capital (X = Date, Y = Severity)
Vinland Capital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sonae (X = Date, Y = Severity)
Sonae cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vinland Capital
Sonae
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.