Comparison Overview
boAt Lifestyle
boAt Lifestyle
Gurgaon, 122008, IN
Last Update: 01/03/2026
boAt set its sail back in 2016. Both our founders, Aman Gupta and Sameer Mehta, realized the massive gaps in the audio and wearable market of India and hence founded boAt with the vision of making a lifestyle brand, that enhances the quality of life through audio and we...
Apple
1 Apple Park Way, Cupertino, 95014, US
Last Update: 10/09/2026
We’re a diverse collective of thinkers and doers, continually reimagining what’s possible to help us all do what we love in new ways. And the same innovation that goes into our products also applies to our practices — strengthening our commitment to leave the world bett...
Compliance Ranges Comparison
boAt Lifestyle
Apple
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for boAt Lifestyle in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Apple has 2521.36% more incidents than the average of all companies with at least one recorded incident.
Incident History - boAt Lifestyle (X = Date, Y = Severity)
boAt Lifestyle cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Apple (X = Date, Y = Severity)
Apple cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
boAt Lifestyle
Apple
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.