Comparison Overview
DUKAT

DUKAT
Marijana Čavića 9, Zagreb, undefined, 10000, HR
Last Update: 11/01/2026
Već 110 godina posvećeni smo potrošačima i samo najboljem mlijeku. Oduvijek nam je bilo važno čuti i razumjeti kako možemo obogatiti živote naših potrošača i biti im podrška i oslonac u svakodnevnom životu. Naša posvećenost potrošaču i svakoj kapi mlijeka oduvijek je bi...

Seara
Avenida Marginal Direita do Tietê 500, São Paulo, SP, BR, 05118100
Last Update: 14/09/2026
Presente há mais de 65 anos nos lares brasileiros, a Seara tem um dos portfólios mais diversificados do setor de alimentos - com opções que vão de proteína animal (frango e suínos) a pratos prontos, margarinas, pizzas, frios, lanches prontos, embutidos e proteína vegeta...
Compliance Ranges Comparison

DUKAT







Seara






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for DUKAT in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Seara in 2026.
Incident History - DUKAT (X = Date, Y = Severity)
DUKAT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Seara (X = Date, Y = Severity)
Seara cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DUKAT

Seara
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.