Comparison Overview
Innoval Technology
Innoval Technology
Innoval Technology, Banbury, Oxon, OX16 1TQ, GB
Last Update: 30/12/2025
At Innoval, knowledge is our business. As aluminium consultants, we’re here to share our expertise to help you develop products and processes that are better for people and for the planet. We believe that all products should be good for people and for the planet. We ar...
Xerox
201 Merritt 7, Norwalk, Connecticut, US
Last Update: 13/09/2026
Xerox is a global technology company with more than 120 years of innovation leadership. We design, manufacture, deliver, and support print, IT, and digital services for nearly 200,000 clients worldwide. Our integrated, AI-powered portfolio includes managed and product...
Compliance Ranges Comparison
Innoval Technology
Xerox
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Innoval Technology in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Xerox in 2026.
Incident History - Innoval Technology (X = Date, Y = Severity)
Innoval Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Xerox (X = Date, Y = Severity)
Xerox cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Innoval Technology
Xerox
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.