Comparison Overview
ATL Insurance Group
ATL Insurance Group
643 MacGregor St, Upper Mount Gravatt, 4122, AU
Last Update: 27/02/2026
With over 15 years of experience, ATL Insurance Group is a niche transport operator underwriting agency, delivering comprehensive Heavy Motor Transport insurance solutions and expertise. We partner with brokers to ensure transport operators receive the best coverage and...
Sunshine Insurance Group
朝外大街, 朝阳区, 100020, CN
Last Update: 04/09/2026
Established in July 2005, Sunshine Insurance Group has experienced sustainable development, now ranking among the Top 7 insurance groups in China, with an annual business income of $12.6 billion in 2016. Sunshine is composed of Property and Casualty Insurance, Life Insu...
Compliance Ranges Comparison
ATL Insurance Group
Sunshine Insurance Group
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for ATL Insurance Group in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Sunshine Insurance Group in 2026.
Incident History - ATL Insurance Group (X = Date, Y = Severity)
ATL Insurance Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sunshine Insurance Group (X = Date, Y = Severity)
Sunshine Insurance Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ATL Insurance Group
Sunshine Insurance Group
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.