Comparison Overview
BMW Singapore
BMW Singapore
1 Harbourfront Ave, Singapore, 098632, SG
Last Update: 02/12/2025
Established in 1985, BMW Singapore is an extremely diverse organisation with nearly 180 employees, representing 20 nationalities, of which nearly 50% are female. It is also a regional hub for strategic corporate functions like the BMW Group Treasury Centre, BMW Financia...
Joyson Group
99， Qingyi Road, Ningbo, Zhejiang, CN, 315000
Last Update: 11/09/2026
Joyson Group is a young, ambitious high-tech company, its headquarter is located in Ningbo, China. With more than 100 bases in 30 countries, over 40000 employees globally. Founded in 2004, Joyson 's main products used to be automotive functional components. Since 201...
Compliance Ranges Comparison
BMW Singapore
Joyson Group
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for BMW Singapore in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Joyson Group in 2026.
Incident History - BMW Singapore (X = Date, Y = Severity)
BMW Singapore cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Joyson Group (X = Date, Y = Severity)
Joyson Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BMW Singapore
Joyson 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.