Comparison Overview
Grupo UPAX
Grupo UPAX
Periférico Sur 4277, Tlalpan, 14210, MX
Last Update: 27/01/2026
Somos UPAX, la house of brands que enciende la evolución empresarial de más de 360 compañías en México. Nuestras ocho Unidades de Negocio integran investigación e inteligencia de mercado, creatividad experiencial y activaciones de marca, junto con desarrollo de tecnolog...
Alvarez & Marsal
600 Madison Avenue, New York, 10022, US
Last Update: 13/09/2026
Alvarez & Marsal is a leading global professional services firm dedicated to helping organizations tackle their most complex business issues, maximize stakeholder value, and deliver sustainable change. Privately held since its founding in 1983, clients select us for o...
Compliance Ranges Comparison
Grupo UPAX
Alvarez & Marsal
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Grupo UPAX in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Alvarez & Marsal in 2026.
Incident History - Grupo UPAX (X = Date, Y = Severity)
Grupo UPAX cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alvarez & Marsal (X = Date, Y = Severity)
Alvarez & Marsal cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grupo UPAX
Alvarez & Marsal
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.