Comparison Overview
Vitec Futursoft

Vitec Futursoft
Maistraatinportti 1, Helsinki, 00240, FI
Last Update: 14/09/2026
We've been delivering innovative ERP solutions for the automotive and machinery sectors since 1998. Our flagship products, AutoFutur and KoneFutur, streamline operations for workshops and spare parts businesses, enhancing efficiency and profitability. Building on this...

IGT
6355 S Buffalo Dr, Las Vegas, NV, US, 89113
Last Update: 15/09/2026
IGT is a leading global provider of gaming, digital and financial technology solutions, formed through the combination of International Game Technology PLC’s Gaming & Digital Business and Everi Holdings Inc. IGT’s offering spans gaming machines, game content and systems...
Compliance Ranges Comparison

Vitec Futursoft







IGT






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Vitec Futursoft in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for IGT in 2026.
Incident History - Vitec Futursoft (X = Date, Y = Severity)
Vitec Futursoft cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IGT (X = Date, Y = Severity)
IGT cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Vitec Futursoft

IGT
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.