Comparison Overview
Digital Hubs I Bayer
Digital Hubs I Bayer
Kaiser-Wilhelm Allee 1, Leverkusen, North Rhine-Westphalia, DE, 51373
Last Update: 13/04/2026
Digital Hubs is the digital accelerator at Bayer that transform Life Science. We create data-driven solutions that transform global agriculture, medicine and have a real impact on health. Locations: 📍#DHubWarsaw - Poland 📍#DHubBangalore - India
Eastman
200 South Wilcox Drive, Kingsport, Tennessee, US, 37662
Last Update: 07/09/2026
Founded in 1920, Eastman is a global specialty materials company that produces a broad range of products found in items people use every day. With the purpose of enhancing the quality of life in a material way, Eastman works with customers to deliver innovative products...
Compliance Ranges Comparison
Digital Hubs I Bayer
Eastman
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Digital Hubs I Bayer in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Eastman in 2026.
Incident History - Digital Hubs I Bayer (X = Date, Y = Severity)
Digital Hubs I Bayer cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Eastman (X = Date, Y = Severity)
Eastman cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Digital Hubs I Bayer
Eastman
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.