Comparison Overview
Hikvision Nordic
Hikvision Nordic
Copenhagen, 2620, DK
Last Update: 15/02/2026
Hikvision is the world’s leading provider of innovative video surveillance products and solutions. By the end of 2019, Hikvision now has 40403 employees, 19065 of whom are R&D engineers. The company annually invests 7 – 8% of its annual sales revenue to research and de...
Haier
1 Haier Rd, Laoshan District., Qingdao, 266103, CN
Last Update: 13/09/2026
Established in 1984, Haier Group is a world-leading provider of solutions to better life. Focusing on user experience, Haier has been included on the list of BrandZ™ Top 100 Most Valuable Global Brands for two consecutive years as the world’s first and only IoT ecosyste...
Compliance Ranges Comparison
Hikvision Nordic
Haier
Benchmark & Cyber Underwriting Signals
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Hikvision Nordic in 2026.
Incidents vs Appliances, Electrical, and Electronics Manufacturing Industry Avg (This Year)
No incidents recorded for Haier in 2026.
Incident History - Hikvision Nordic (X = Date, Y = Severity)
Hikvision Nordic cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Haier (X = Date, Y = Severity)
Haier cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hikvision Nordic
Haier
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.