Comparison Overview
Apec Occitanie
Apec Occitanie
18, Rue Lafayette, None, Toulouse, Occitanie, FR, 31000
Last Update: 29/01/2026
🎯 Bienvenue sur la page de l’Apec Occitanie ! Présente à Toulouse, Montpellier, Nîmes et Perpignan, notre équipe de 63 collaborateurs et collaboratrices est mobilisée pour accompagner les cadres, les jeunes diplômé·e·s (Bac + 3 et +) et les entreprises dans leurs proj...
Randstad
Diemermere 25, Diemen, 1112 TC, NL
Last Update: 08/09/2026
Randstad is the world’s largest talent company and a partner of choice to clients. We are committed to providing equitable opportunities to people from all backgrounds and help them remain relevant in the rapidly changing world of work. We have a deep understanding of t...
Compliance Ranges Comparison
Apec Occitanie
Randstad
Benchmark & Cyber Underwriting Signals
Incidents vs Human Resources Services Industry Avg (This Year)
No incidents recorded for Apec Occitanie in 2026.
Incidents vs Human Resources Services Industry Avg (This Year)
No incidents recorded for Randstad in 2026.
Incident History - Apec Occitanie (X = Date, Y = Severity)
Apec Occitanie cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Randstad (X = Date, Y = Severity)
Randstad cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Apec Occitanie
Randstad
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.