Comparison Overview
Brézillon
Brézillon
128, Rue de Beauvais, Margny-lès-Compiègne, 60280, FR
Last Update: 04/12/2025
Avec 115 collaborateurs répartis sur toute la France, Brézillon engage ses expertises et son savoir-faire en génie environnemental pour préserver et restaurer les territoires. Les équipes de Brézillon accompagnent la reconversion des sites dégradés et apportent leurs ...
WM
800 Capitol St, Suite 3000, Houston, Texas, US, 77002
Last Update: 13/09/2026
WM is North America's leading provider of integrated environmental solutions. We partner with our customers and communities to manage and reduce waste from collection to disposal while recovering valuable resources and creating clean, renewable energy. We are on a quest...
Compliance Ranges Comparison
Brézillon
WM
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Brézillon in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for WM in 2026.
Incident History - Brézillon (X = Date, Y = Severity)
Brézillon cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WM (X = Date, Y = Severity)
WM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Brézillon
WM
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.