Comparison Overview
OnePlus
OnePlus
Tairan 8th Road, Shenzhen, 518000, CN
Last Update: 01/04/2026
This is our story. It’s a story that starts with a group of innovators. Back in 2013, the smartphone industry was stagnating. We imagined a better kind of smartphone and a better way of doing things. Our goal was to build a smartphone we would want to use ourselves. Wha...
Motorola Mobility (a Lenovo Company)
222 W. Merchandise Mart Plaza, Chicago, 60654, US
Last Update: 11/09/2026
As part of the Lenovo family, Motorola Mobility is creating innovative smartphones and accessories designed with the consumer in mind. That’s why we’re looking for the thinkers, innovators and problem solvers who believe in working together to challenge the status quo. ...
Compliance Ranges Comparison
OnePlus
Motorola Mobility (a Lenovo Company)
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for OnePlus in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Motorola Mobility (a Lenovo Company) in 2026.
Incident History - OnePlus (X = Date, Y = Severity)
OnePlus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Motorola Mobility (a Lenovo Company) (X = Date, Y = Severity)
Motorola Mobility (a Lenovo Company) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OnePlus
Motorola Mobility (a Lenovo Company)
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.