Comparison Overview
Citrosuco
Citrosuco
BR
Last Update: 25/02/2026
We are a 100% Brazilian-owned closed-capital company. We operate at all stages of the orange juice production chain, from cultivating fruit to the delivery of our products. We are an export-oriented company and our customers, mainly in the beverage segment, are located ...
JBS
Avenida Marginal Direita do Tietê, 500, São Paulo, 05118-100, BR
Last Update: 11/09/2026
Na JBS, a gente alimenta um futuro melhor. Tudo começou com uma pequena porta de um açougue, há mais de 70 anos. E, daquela porta, surgiram muitas outras. Foi acreditando em coisas simples, em fazer sempre melhor, contando com o trabalho de muita gente e abrindo portas...
Compliance Ranges Comparison
Citrosuco
JBS
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Citrosuco in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for JBS in 2026.
Incident History - Citrosuco (X = Date, Y = Severity)
Citrosuco cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JBS (X = Date, Y = Severity)
JBS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Citrosuco
JBS
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.