Comparison Overview
Bosch Research
Bosch Research
Robert-Bosch-Campus 1, Renningen, 71272, DE
Last Update: 03/03/2026
Bosch Research serves as the central hub for innovation within Bosch. With a global team of around 1,800 experts in the Research and Advanced Engineering division, Bosch collaboratively develops the future generation of products and services across all its business sect...
Utrecht University
Heidelberglaan 6, Utrecht, Utrecht, 3512, NL
Last Update: 02/04/2026
At Utrecht University (UU), we are working towards a better world. We do this by researching complex issues beyond the borders of disciplines. We put thinkers in contact with doers, so new insights can be applied. We give students the space to develop themselves. In so ...
Compliance Ranges Comparison
Bosch Research
Utrecht University
Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Bosch Research in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Utrecht University in 2026.
Incident History - Bosch Research (X = Date, Y = Severity)
Bosch Research cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Utrecht University (X = Date, Y = Severity)
Utrecht University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bosch Research
Utrecht University
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.