Comparison Overview
Ryan Homes
Ryan Homes
11700 Plaza America Dr, Reston, Virginia, 20190, US
Last Update: 01/03/2026
Where you live is our life's work. Home is where the heart is— yours and ours. Our passion—and our purpose—is making places people love to call home. What began in 1948 as a small, family-run business in Pittsburgh has evolved into one of the top five home builders i...
Kiewit
1550 Mike Fahey St., Omaha, 68102, US
Last Update: 15/09/2026
At Kiewit, the projects we deliver make a difference, and we offer opportunities for you to make one, too. Our construction and engineering professionals work on some of the industry’s most complex, challenging and rewarding projects – whether it’s boring tunnels throug...
Compliance Ranges Comparison
Ryan Homes
Kiewit
Benchmark & Cyber Underwriting Signals
Incidents vs Construction Industry Avg (This Year)
No incidents recorded for Ryan Homes in 2026.
Incidents vs Construction Industry Avg (This Year)
Kiewit has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Ryan Homes (X = Date, Y = Severity)
Ryan Homes cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kiewit (X = Date, Y = Severity)
Kiewit cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ryan Homes
Kiewit
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.