Comparison Overview
Foxconn iAI
Foxconn iAI
12001 Braun Rd, Mount Pleasant, 53177, US
Last Update: 16/12/2025
Our mission is to create a worry-free world where smart solutions simplify work, reduce worry, and eliminate waste. About Foxconn iAI At Foxconn iAI, we refer to ourselves as the "manufacturing problem solvers" We were founded in 2019 by Dr. Jay Lee as the industrial A...
Zoho
Zoho Corporation Pvt. Ltd, Estancia IT Park, Plot No. 140 & 151,, Chennai, 603202, IN
Last Update: 13/09/2026
Zoho offers beautifully smart software to help you grow your business. With over 100 million users worldwide, Zoho's 55+ products aid your sales and marketing, support and collaboration, finance, and recruitment needs—letting you focus only on your business. Zoho respec...
Compliance Ranges Comparison
Foxconn iAI
Zoho
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Foxconn iAI in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Zoho in 2026.
Incident History - Foxconn iAI (X = Date, Y = Severity)
Foxconn iAI cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zoho (X = Date, Y = Severity)
Zoho cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Foxconn iAI
Zoho
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.