Comparison Overview
Tetra Tech Solid Waste
Tetra Tech Solid Waste
3475 E Foothill Blvd, Pasadena, 91107, US
Last Update: 01/12/2025
Our solid waste experts work with biogas, landfill gas, industrial, organics management, air quality, and transfer, and recycling and processing clients across North America. Our clients range from rural communities to large metropolitan solid waste authorities and incl...
SUEZ
La Défense, Paris, 92040, FR
Last Update: 13/09/2026
We provide essential services in the water and waste sectors to preserve resources and improve quality of life wherever we operate. As a global player for over 160 years, we support public and private actors with resilient and innovative solutions. With a presence in ...
Compliance Ranges Comparison
Tetra Tech Solid Waste
SUEZ
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Tetra Tech Solid Waste in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for SUEZ in 2026.
Incident History - Tetra Tech Solid Waste (X = Date, Y = Severity)
Tetra Tech Solid Waste cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SUEZ (X = Date, Y = Severity)
SUEZ cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tetra Tech Solid Waste
SUEZ
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.