Comparison Overview
CredRisk Marine
CredRisk Marine
Av. Dra. Ruth Cardoso, 8501, São Paulo, São Paulo, 05425-070, BR
Last Update: 21/12/2025
A CredRisk Marine é uma corretora de seguros independente focada em fornecer soluções especializadas em Seguros Marítimos para o Comércio, Setor de Transporte Marítimo, e Indústria de Logística. A CredRisk Marine faz parte da CredRisk Seguros - www.credriskseguros.com ...
Porto
Avenida Rio Branco, 1489, Sao Paulo, SP, BR, 01205-001
Last Update: 03/09/2026
A Porto é mais que uma seguradora, é um ecossistema de soluções de serviços de proteção com tecnologia embarcada, para melhorar e facilitar a experiência do cliente. Com mais de 70 anos de mercado, a atuação da companhia se concentra hoje em quatro pilares estratégicos ...
Compliance Ranges Comparison
CredRisk Marine
Porto
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for CredRisk Marine in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Porto in 2026.
Incident History - CredRisk Marine (X = Date, Y = Severity)
CredRisk Marine cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Porto (X = Date, Y = Severity)
Porto cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
CredRisk Marine
Porto
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.