Comparison Overview
Grange Insurance Solutions
Grange Insurance Solutions
375 Charles St, North Perth, Western Australia, 6006, AU
Last Update: 31/03/2026
At Grange Insurance Solutions, we provide you with exceptional customer service and specialist general insurance advice, to help save you time and provide you with the peace of mind you deserve. As your local brokers, we’re here to support you and your business. We le...
Great Eastern
1 Pickering Street , Singapore, 048659, SG
Last Update: 05/09/2026
For 117 years, we have been helping customers across generations by protecting, preserving and growing what matters to them. As One Great Eastern Group today, we are enabling the goals of over 15.5 million customers by taking care of their needs across life, health, wea...
Compliance Ranges Comparison
Grange Insurance Solutions
Great Eastern
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Grange Insurance Solutions in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Great Eastern in 2026.
Incident History - Grange Insurance Solutions (X = Date, Y = Severity)
Grange Insurance Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Great Eastern (X = Date, Y = Severity)
Great Eastern cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grange Insurance Solutions
Great Eastern
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.