Comparison Overview
Grand Parade
Grand Parade
Kotlarska 11, Krakow, malopolskie, 31-539, PL
Last Update: 10/04/2026
We’re Grand Parade. Hi. You might have heard of us before, and if you haven’t, don’t worry, read on, and you’ll get the lowdown. We build products used by tens of millions of people every week all over the world – and we’re pretty proud of that. And to build those p...
CenturyLink
100 CenturyLink Drive, Monroe, 71201, US
Last Update: 13/09/2026
CenturyLink (NYSE: CTL) is a technology leader delivering hybrid networking, cloud connectivity, and security solutions to customers around the world. Through its extensive global fiber network, CenturyLink provides secure and reliable services to meet the growing digit...
Compliance Ranges Comparison
Grand Parade
CenturyLink
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Grand Parade in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for CenturyLink in 2026.
Incident History - Grand Parade (X = Date, Y = Severity)
Grand Parade cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CenturyLink (X = Date, Y = Severity)
CenturyLink cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grand Parade
CenturyLink
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.