Comparison Overview
Horizon

Horizon
590 E Middlefield Rd, Mountain View, California, US, 94043
Last Update: 01/04/2026
Omnissa Horizon is an industry-leading solution designed to revolutionize virtual desktops and apps delivery – on-premises, in the cloud, or in hybrid environments.

Wolters Kluwer
Zuidpoolsingel 2, Alphen aan den Rijn, 2400 BA, NL
Last Update: 10/09/2026
Wolters Kluwer (EURONEXT: WKL) is a global leader in information, software solutions, and services for professionals in healthcare; tax and accounting; financial and corporate compliance; legal and regulatory; corporate performance and ESG. We help our customers make cr...
Compliance Ranges Comparison

Horizon







Wolters Kluwer






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

Horizon

Wolters Kluwer
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.