Comparison Overview
QBE Insurance
QBE Insurance
388 George Street, Sydney, New South Wales, AU, 2000
Last Update: 05/09/2026
At QBE we’re driven by our purpose of enabling a more resilient future. QBE is an international insurer and reinsurer headquartered in Sydney, Australia, with local presence in 26 countries. We don't just see ourselves as an insurer, but a partner to our customers i...
Vienna Insurance Group (VIG)
Schottenring 30, Vienna, 1010, AT
Last Update: 03/04/2026
Vienna Insurance Group (VIG) is the leading insurance group in the entire Central and Eastern European (CEE) region. More than 50 insurance companies and pension funds in 30 countries form a Group with a long-standing tradition, strong brands and close customer relation...
Compliance Ranges Comparison
QBE Insurance
Vienna Insurance Group (VIG)
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for QBE Insurance in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Vienna Insurance Group (VIG) in 2026.
Incident History - QBE Insurance (X = Date, Y = Severity)
QBE Insurance cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vienna Insurance Group (VIG) (X = Date, Y = Severity)
Vienna Insurance Group (VIG) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
QBE Insurance
Vienna Insurance Group (VIG)
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.