Comparison Overview
SoHi Meat Solutions
SoHi Meat Solutions
, , Santarém, , PT,
Last Update: 22/04/2026
Fundada em 2017, a SOHI é resultado da joint-venture entre a MC e a Hilton Foods. Operando em Santarém desde 2002 para fornecer carnes frescas pré-embaladas, em 2013 expandiu a sua capacidade e modernizou-se através da instalação de novas tecnologias. A empresa investe ...
Bunge
1391 Timberlake Manor Pkwy, Chesterfield, Missouri, US, 63017
Last Update: 13/09/2026
At Bunge (NYSE: BG), our purpose is to connect farmers to consumers to deliver essential food, feed and fuel to the world. As a premier agribusiness solutions provider, our team of ~37,000 dedicated employees partner with farmers across the globe to move agricultural co...
Compliance Ranges Comparison
SoHi Meat Solutions
Bunge
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for SoHi Meat Solutions in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Bunge in 2026.
Incident History - SoHi Meat Solutions (X = Date, Y = Severity)
SoHi Meat Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bunge (X = Date, Y = Severity)
Bunge cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SoHi Meat Solutions
Bunge
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.