Comparison Overview
AB InBev
AB InBev
Brouwerijplein 1, Leuven, BE, 3000
Last Update: 13/09/2026
As a company, we dream big to create a future with more cheers. We are always looking to serve up new ways to meet life’s moments, move our industry forward and make a meaningful impact in the world. We are committed to building great brands that stand the test of time ...
Kohler Co.
444 Highland Drive, Kohler, Wisconsin, US, 53044
Last Update: 13/09/2026
We’re a community of creators. Status quo busters. Difference makers. For more than 150 years, we’ve built our business on a singular mission—helping people live gracious, healthy, and sustainable lives. Thanks to the passion, craftsmanship, and ingenuity of our ass...
Compliance Ranges Comparison
AB InBev
Kohler Co.
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for AB InBev in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Kohler Co. in 2026.
Incident History - AB InBev (X = Date, Y = Severity)
AB InBev cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kohler Co. (X = Date, Y = Severity)
Kohler Co. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AB InBev
Kohler Co.
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.