Comparison Overview
MG Dyess
MG Dyess
7159 Hwy 35, Bassfield, 39421, US
Last Update: 25/03/2026
A family company with Quanta backing, MG Dyess was founded in 1992 in small-town Mississippi. Back then, customers in the region were looking for an open shop contractor that could handle rough, heavy terrain, and we responded to that call by building a team that could ...
VINCI Construction
1973, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 16/09/2026
Premier groupe français et acteur mondial de premier plan de la construction, VINCI Construction réunit plus de 830 entreprises et près de 69000 collaborateurs dans une centaine de pays. Ses expertises s’étendent à l’ensemble des métiers du bâtiment, du génie civil, et ...
Compliance Ranges Comparison
MG Dyess
VINCI Construction
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for MG Dyess in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for VINCI Construction in 2026.
Incident History - MG Dyess (X = Date, Y = Severity)
MG Dyess cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VINCI Construction (X = Date, Y = Severity)
VINCI Construction cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
MG Dyess
VINCI Construction
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.