Comparison Overview
Hubbis
Hubbis
Queen's Road Central, Hong Kong, 0000, HK
Last Update: 04/04/2026
We focus on the Asian wealth management industry and produce high-quality, localised content that is practical and independent; This includes news, articles, white papers, thought leadership and conference-linked content, and is available in multiple formats including v...
Shriram Finance Limited
Wockhardt Towers, Level-3, West Wing, C-2, G-Block, Bandra-Kurla Complex, Bandra (East), Mumbai, IN, 400051
Last Update: 12/09/2026
Shriram Finance is the country’s biggest retail NBFC offering credit solutions for commercial vehicles, two-wheeler loans, car loans, home loans, gold loans, personal and small business loans. We are part of the 50-year-old Shriram Group, a financial conglomerate that h...
Compliance Ranges Comparison
Hubbis
Shriram Finance Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Hubbis in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Shriram Finance Limited in 2026.
Incident History - Hubbis (X = Date, Y = Severity)
Hubbis cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Shriram Finance Limited (X = Date, Y = Severity)
Shriram Finance Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hubbis
Shriram Finance Limited
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.