Comparison Overview
MENARD USA
MENARD USA
151 Roessler Rd, Pittsburgh, 15220, US
Last Update: 11/03/2026
Menard USA is a design-build specialty contractor offering ground improvement for sites with problematic soil conditions. Combining creative design and innovative techniques, Menard delivers practical, economical, and sustainable solutions that can be attractive alterna...
Burns & McDonnell
9400 Ward Pkwy, Kansas City, 64114, US
Last Update: 13/09/2026
At Burns & McDonnell, our engineers, construction professionals, architects, planners, technologists and scientists do more than plan, design and construct. With a mission unchanged since 1898 — make our clients successful — we partner with you on the toughest challenge...
Compliance Ranges Comparison
MENARD USA
Burns & McDonnell
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for MENARD USA in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Burns & McDonnell in 2026.
Incident History - MENARD USA (X = Date, Y = Severity)
MENARD USA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Burns & McDonnell (X = Date, Y = Severity)
Burns & McDonnell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MENARD USA
Burns & McDonnell
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.