Comparison Overview
Sully-Miller Contracting Co.

Sully-Miller Contracting Co.
135 South State College Blvd., Brea, CA, 92821, US
Last Update: 23/01/2026
Part of Colas USA, Sully-Miller Contracting Company is one of the premier road and highway contractors, rail & intermodal, seaport, airport, federal/military and specialty contractors in Southern California. You will not find a more integrated and versatile general con...

D.R. Horton
1341 Horton Circle, Arlington, 76011, US
Last Update: 13/09/2026
America's Builder is a lofty title, but it's a goal we work toward every day. D.R. Horton started in 1978 in Fort Worth, Texas, and has grown into a national Fortune 500 company. Since 2002, D.R. Horton has been the number one homebuilder in America. We build across ...
Compliance Ranges Comparison

Sully-Miller Contracting Co.







D.R. Horton






Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Sully-Miller Contracting Co. in 2026.
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for D.R. Horton in 2026.
Incident History - Sully-Miller Contracting Co. (X = Date, Y = Severity)
Sully-Miller Contracting Co. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - D.R. Horton (X = Date, Y = Severity)
D.R. Horton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sully-Miller Contracting Co.

D.R. Horton
FAQ
Latest Global CVEs
A vulnerability was determined in xuxueli xxl-job up to 3.5.0. The impacted element is an unknown function of the file /jobgroup/insert. This manipulation of the argument Name causes cross site scripting. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was found in Moore Threads MTT S80 Driver Package 340.150. The affected element is the function sub_140006F0C in the library mtdispkm64.sys of the component IOCTL Handler. The manipulation results in improper privilege management. Attacking locally is a requirement. The vendor was contacted early about this disclosure but did not respond in any way.
vLLM Mooncake connector through 0.29.0 fails to properly manage GPU KV cache block ownership when concurrent child requests share a single transfer ID in prefill/decode disaggregated deployments. Attackers can trigger GPU memory exhaustion by submitting completion requests with multiple prompts, causing orphaned KV cache blocks to accumulate until process restart and eventually preventing legitimate requests from executing.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1978-L1989
- https://github.com/vllm-project/vllm/pull/49796
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-gpu-kv-cache-leak-via-mooncake-transfer-id-collision
vLLM through 0.29.0 fails to validate the tp_size parameter in kv_transfer_params on OpenAI-compatible completion endpoints, allowing attackers to allocate unbounded memory. Attackers can supply arbitrary tp_size values in prefill/decode disaggregated deployments to exhaust memory and trigger kernel OOM-kill of the decode worker process.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/utils.py#L569-L573
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/metadata.py#L277
- https://github.com/vllm-project/vllm/pull/51137
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-unvalidated-nixl-tp-size
vLLM through 0.29.0 contains a resource exhaustion vulnerability in MooncakeConnector where rejected prefill requests create ownerless transfer placeholders that are never reclaimed. Attackers can send rejected requests to exhaust sender task pools, causing valid requests to be delayed by up to 480 seconds while health checks continue returning success.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/mooncake/mooncake_connector.py#L1234-L1242
- https://github.com/vllm-project/vllm/pull/51236
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-resource-exhaustion-via-ownerless-mooncake-transfer-placeholders