Comparison Overview
Bühler Group Generation B
Bühler Group Generation B
Gupfenstrasse 5, Uzwil, CH
Last Update: 22/02/2026
Bühler has a purpose, the company has committed to a sustainable future, providing the means for healthy, save and nutritious food as well as mobility and green energy for an ever growing population and creating a better tomorrow together. Generation B stands for "Be th...
John Deere
Moline, 61265, US
Last Update: 13/09/2026
It doesn’t matter if you’ve never driven a tractor, mowed a lawn, or operated a dozer. With John Deere’s role in helping produce food, fiber, fuel, and infrastructure, we work for every single person on the planet. It all started nearly 200 years ago with a steel plow...
Compliance Ranges Comparison
Bühler Group Generation B
John Deere
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Bühler Group Generation B in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for John Deere in 2026.
Incident History - Bühler Group Generation B (X = Date, Y = Severity)
Bühler Group Generation B cyber incidents detection timeline including parent company and subsidiaries.
Incident History - John Deere (X = Date, Y = Severity)
John Deere cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bühler Group Generation B
John Deere
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.