Comparison Overview
BMW India
BMW India
Building No. 8, Tower B, 7th Floor, Gurgaon, Haryana, 122 002, IN
Last Update: 27/02/2026
BMW is the world’s leading manufacturer of premium luxury automobiles. It has not only been at the forefront of innovation and technology, but has a rich history shaped by visionaries, pioneers and distinguished designers. Along with automobiles, BMW India comprise of f...
Iveco Group
Via Puglia 35, Torino, 10156, IT
Last Update: 13/09/2026
Iveco Group N.V. (MI: IVG) is the home of unique people and brands that power your business and mission to advance a more sustainable society. The seven brands are each a major force in its specific business: IVECO, a pioneering commercial vehicles brand that designs, m...
Compliance Ranges Comparison
BMW India
Iveco Group
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for BMW India in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Iveco Group in 2026.
Incident History - BMW India (X = Date, Y = Severity)
BMW India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Iveco Group (X = Date, Y = Severity)
Iveco Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BMW India
Iveco Group
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.