Comparison Overview
Total Cyber-Sec
Total Cyber-Sec
Camino a Santa Teresa 187C, 14010, Parques del Pedregal, CDMX, 14000, MX
Last Update: 22/03/2026
Somos una empresa de Grupo Salinas con un equipo de profesionales en Seguridad de la Información con más de 15 años de experiencia que nos respalda en los sectores: financieros, retail, telecomunicaciones, entre otros. Nuestra misión es brindar a nuestros clientes solu...
Orange Business
La Plaine Saint Denis, Paris, FR, 93457 Cedex
Last Update: 09/09/2026
At Orange Business, our ambition is to become the leading european Network and Digital Integrator by leveraging our proven expertise in next-generation connectivity solutions, the cloud and cybersecurity. Our 30,000 women and men are present in 65 countries, where ever...
Compliance Ranges Comparison
Total Cyber-Sec
Orange Business
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Total Cyber-Sec in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Orange Business in 2026.
Incident History - Total Cyber-Sec (X = Date, Y = Severity)
Total Cyber-Sec cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orange Business (X = Date, Y = Severity)
Orange Business cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Total Cyber-Sec
Orange Business
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.