Comparison Overview
Vitec Visitor Systems
Vitec Visitor Systems
Västra Vägen 52, 803 24 Gävle, Gävle, SE
Last Update: 14/09/2026
Vi är en ledande leverantör av affärs- och verksamhetssystem för besöksnäringen – med kunder inom allt från simhallar och nöjesparker till campingplatser och idrottsförvaltningar. Genom våra lösningar hjälper vi våra kunder att ta emot och hantera miljontals gäster varj...
Microsoft
1 Microsoft Way, Redmond, 98052, US
Last Update: 06/09/2026
Every company has a mission. What's ours? To empower every person and every organization to achieve more. We believe technology can and should be a force for good and that meaningful innovation contributes to a brighter world in the future and today. Our culture doesn’t...
Compliance Ranges Comparison
Vitec Visitor Systems
Microsoft
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Vitec Visitor Systems in 2026.
Incidents vs Software Development Industry Avg (This Year)
Microsoft has 2133.01% more incidents than the average of all companies with at least one recorded incident.
Incident History - Vitec Visitor Systems (X = Date, Y = Severity)
Vitec Visitor Systems cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Microsoft (X = Date, Y = Severity)
Microsoft cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Vitec Visitor Systems
Microsoft
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.