Comparison Overview
Exyte
Exyte
Loewentorbogen 9b, Stuttgart, Baden-Württemberg, 70376, DE
Last Update: 03/11/2025
As an engineering, procurement, and construction (EPC) company, we design and deliver high-tech facilities for our clients. For over 100 years, we’ve been driven by one idea: Applying technology to build cutting-edge facilities where it has the most significant impact o...
MRV
Av. Prof. Mario Werneck, 621, Belo Horizonte, 30.455-610, BR
Last Update: 16/09/2026
Some 45 years ago, we set out with the ambitious goal of providing affordable housing, working to make Brazilian dreams come true. Over the last few years, we have crafted and shaped our story, becoming a brand-leading platform that offers a variety of housing solutions...
Compliance Ranges Comparison
Exyte
MRV
Benchmark & Cyber Underwriting Signals
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for Exyte in 2026.
Incidents vs Civil Engineering Industry Avg (This Year)
No incidents recorded for MRV in 2026.
Incident History - Exyte (X = Date, Y = Severity)
Exyte cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MRV (X = Date, Y = Severity)
MRV cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Exyte
MRV
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.