Comparison Overview
Lido
Lido
Am Messeplatz 1, Raunheim, 65479, DE
Last Update: 18/02/2026
Lido presents a new generation of aviation solutions to support you in increasing the safety and efficiency of your entire mission – both on the ground and in the air. Lido Flight Planning Solutions: Our holistic approach of integrating data from various sources direct...
Thoughtworks
200 E Randolph St, 25th Floor, Chicago, IL, US, 60601-6501
Last Update: 14/09/2026
We are a global technology consultancy that delivers extraordinary impact by blending design, engineering and AI expertise. For 30 years, our commitment to design-led thinking, engineering excellence and innovation means we prioritize people, build teams with strong te...
Compliance Ranges Comparison
Lido
Thoughtworks
Benchmark & Cyber Underwriting Signals
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for Lido in 2026.
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for Thoughtworks in 2026.
Incident History - Lido (X = Date, Y = Severity)
Lido cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Thoughtworks (X = Date, Y = Severity)
Thoughtworks cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Lido
Thoughtworks
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.