Comparison Overview
ALIZENT
ALIZENT
Coeur Défense, 110 Esplanade du Général de Gaulle, Paris La Défense, undefined, 92931, FR
Last Update: 02/04/2026
Alizent provides innovative and differentiating digital solutions to support industries in their digital transformation for sustainable performance. By improving their logistics, we make it easier for them, for example, to reduce their carbon footprint; by optimising t...
EPAM Systems
41 University Drive Suite 202, Newtown, PA, US, 18940
Last Update: 07/09/2026
Since 1993, EPAM Systems, Inc. (NYSE: EPAM) has used its software engineering expertise to become a leading global provider of digital engineering, cloud and AI-enabled transformation services, and a leading business and experience consulting partner for global enterpri...
Compliance Ranges Comparison
ALIZENT
EPAM Systems
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for ALIZENT in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for EPAM Systems in 2026.
Incident History - ALIZENT (X = Date, Y = Severity)
ALIZENT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EPAM Systems (X = Date, Y = Severity)
EPAM Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ALIZENT
EPAM Systems
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.