Comparison Overview
Koodoo
Koodoo
Scale Space, 58 Wood Lane, London, England, W12 7RZ, GB
Last Update: 05/03/2026
Koodoo powers 1m+ mortgage comparison searches monthly for leading brands like Compare the Market, Experian & GoCompare. We are building a future where customers can approach their mortgage with confidence not dread. Follow our journey transforming mortgage journeys wit...
Commonwealth Bank
., Sydney, 2000, AU
Last Update: 12/09/2026
Australia’s leading provider of financial services including retail, premium, business and institutional banking, funds management, superannuation, insurance, investment and sharebroking products and services. We are a business with more than 800,000 shareholders and o...
Compliance Ranges Comparison
Koodoo
Commonwealth Bank
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Koodoo in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Commonwealth Bank has 94.17% more incidents than the average of all companies with at least one recorded incident.
Incident History - Koodoo (X = Date, Y = Severity)
Koodoo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Commonwealth Bank (X = Date, Y = Severity)
Commonwealth Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Koodoo
Commonwealth Bank
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.