Comparison Overview
Elastec Vacuum Systems
Elastec Vacuum Systems
1309 West Main Street, Carmi, 62821, US
Last Update: 30/11/2025
Elastec manufactures vacuum systems for industrial, municipal, and oil spill cleanup. Easy to tow and maneuver in congested workspaces, these rugged vacuum systems are purpose-built to clean up oil, liquids, solids, and sludge. Our trailer-mounted vacuum systems are des...
Bureau Veritas
4 Place des Saisons, Paris, Courbevoie, FR, 92400
Last Update: 14/09/2026
Bureau Veritas is a world leader in Testing, Inspection and Certification. Our mission is at the heart of key challenges: quality, health and safety, environmental protection and social responsibility. Through our wide range of expertise, impartiality and independence, ...
Compliance Ranges Comparison
Elastec Vacuum Systems
Bureau Veritas
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Elastec Vacuum Systems in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Bureau Veritas in 2026.
Incident History - Elastec Vacuum Systems (X = Date, Y = Severity)
Elastec Vacuum Systems cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bureau Veritas (X = Date, Y = Severity)
Bureau Veritas cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Elastec Vacuum Systems
Bureau Veritas
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.