Comparison Overview
Econocom Nederland
Econocom Nederland
Computerweg 22, Utrecht, 3542, NL
Last Update: 26/02/2026
Financiering en services voor werkplekken, audiovisuele- en IT-infrastructuren. Ben je als organisatie op zoek naar professionele ondersteuning op het gebied van de digitale projecten? Dan ben je bij Econocom aan het juiste adres! Met onze duurzame oplossingen voor zow...
Kyndryl
New York City, US
Last Update: 11/09/2026
We have the world’s best talent that design, run, and manage the most advanced and reliable technology infrastructure each day. Together, we think holistically about the health of these vital technology ecosystems. We are a focused, independent company that builds on o...
Compliance Ranges Comparison
Econocom Nederland
Kyndryl
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Econocom Nederland in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Kyndryl has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Econocom Nederland (X = Date, Y = Severity)
Econocom Nederland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kyndryl (X = Date, Y = Severity)
Kyndryl cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Econocom Nederland
Kyndryl
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.