Comparison Overview
eLoyalty, a TeleTech Company
eLoyalty, a TeleTech Company
6500 River Place Blvd, Building 2, Austin, TX, US, 78730
Last Update: 05/03/2026
eLoyalty is now TTEC. TTEC is a global customer experience company that designs, builds and operates captivating omnichannel customer experiences on behalf of the world’s most innovative brands. The Company provides its outcome-based customer engagement solutions throug...
VOIS
London, GB
Last Update: 05/09/2026
VOIS (Vodafone Intelligent Solutions) is a strategic arm of Vodafone Group Plc, creating value for customers by delivering intelligent solutions through Talent, Technology & Transformation. As the largest shared services organisation in the global telco industry, our ...
Compliance Ranges Comparison
eLoyalty, a TeleTech Company
VOIS
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for eLoyalty, a TeleTech Company in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for VOIS in 2026.
Incident History - eLoyalty, a TeleTech Company (X = Date, Y = Severity)
eLoyalty, a TeleTech Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VOIS (X = Date, Y = Severity)
VOIS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
eLoyalty, a TeleTech Company
VOIS
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.