Comparison Overview
PHOENIX Pharma Italia
PHOENIX Pharma Italia
Via Fratelli Di Dio, 2, Novate Milanese, 20026, IT
Last Update: 24/04/2026
Siamo un’impresa della salute che punta all’eccellenza attraverso una crescita strategica e prospettica del business, sempre guardando al benessere delle persone e alla sostenibilità sociale e ambientale, con un forte orientamento all’innovazione e alle evoluzioni del m...
Atacadão
Av. Morvan Dias de Figueiredo, 6169, São Paulo, 02170901, BR
Last Update: 31/03/2026
O Atacadão é uma empresa do Grupo Carrefour Brasil, com mais de 370 unidades de autosserviço e 36 atacados de entrega e centros de distribuição, que garantem o abastecimento de comerciantes, transformadores e consumidores finais, e está em contínua expansão. Com base n...
Compliance Ranges Comparison
PHOENIX Pharma Italia
Atacadão
Benchmark & Cyber Underwriting Signals
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for PHOENIX Pharma Italia in 2026.
Incidents vs Wholesale Industry Avg (This Year)
No incidents recorded for Atacadão in 2026.
Incident History - PHOENIX Pharma Italia (X = Date, Y = Severity)
PHOENIX Pharma Italia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Atacadão (X = Date, Y = Severity)
Atacadão cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PHOENIX Pharma Italia
Atacadão
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.