Comparison Overview
ZAGG, Inc.
ZAGG, Inc.
910 West Legacy Center Drive, Salt Lake City, UT, US, 84103
Last Update: 04/04/2026
Since 2004, ZAGG has been protecting and enhancing your favorite gadgets. From our first InvisibleShield to our latest advances in audio, protection, power, and customization - our goal is to make your life easier and the life of your gadgets longer as we're at the top ...
Samsung Electronics
129 Samsung-ro, Suwon-Si, 443-742, KR
Last Update: 12/09/2026
Samsung Electronics is a global leader in technology, opening new possibilities for people everywhere. Through relentless innovation and discovery, we are transforming the worlds of TVs, smartphones, wearable devices, tablets, digital appliances, network systems, medica...
Compliance Ranges Comparison
ZAGG, Inc.
Samsung Electronics
Benchmark & Cyber Underwriting Signals
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for ZAGG, Inc. in 2026.
Incidents vs Computers and Electronics Manufacturing Industry Avg (This Year)
Samsung Electronics has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - ZAGG, Inc. (X = Date, Y = Severity)
ZAGG, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Samsung Electronics (X = Date, Y = Severity)
Samsung Electronics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ZAGG, Inc.
Samsung Electronics
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.