Comparison Overview
HKT
HKT
39/F, PCCW Tower, TaiKoo Place, 979 King's Road, Quarry Bay, Hong Kong, Hong Kong, undefined, undefined, HK
Last Update: 04/04/2026
HKT is a technology, media, and telecommunication leader with more than 150 years of history in Hong Kong. As the city’s true 5G provider, HKT connects businesses and people locally and globally. Our end-to-end enterprise solutions make us a market-leading digital trans...
Synopsys Inc
675 Almanor Ave, Sunnyvale, 94085, US
Last Update: 11/09/2026
Synopsys is the leader in engineering solutions from silicon to systems, enabling customers to rapidly innovate AI-powered products. We deliver industry-leading silicon design, IP, simulation and analysis solutions, and design services. We partner closely with our cu...
Compliance Ranges Comparison
HKT
Synopsys Inc
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for HKT in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Synopsys Inc in 2026.
Incident History - HKT (X = Date, Y = Severity)
HKT cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Synopsys Inc (X = Date, Y = Severity)
Synopsys Inc cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
HKT
Synopsys Inc
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.