Comparison Overview
Titan Company Limited
Titan Company Limited
#193, Veerasandra,, Electronic City, Bangalore , 560100, IN
Last Update: 14/09/2026
Titan Company Ltd is the organization that brought about a paradigm shift in the Indian watch market when it introduced its futuristic quartz technology, complemented by international styling. With India's two most recognized and loved brands Titan and Tanishq to its cr...
Bunnings
570 Swan Street, Burnley, Victoria, AU, 3121
Last Update: 14/09/2026
We are the leading retailer of home improvement and outdoor living products in Australia & New Zealand and a major supplier to project builders, commercial tradespeople and the housing industry. Our ambition is to provide our customers with the widest range of home imp...
Compliance Ranges Comparison
Titan Company Limited
Bunnings
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Titan Company Limited in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Bunnings in 2026.
Incident History - Titan Company Limited (X = Date, Y = Severity)
Titan Company Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bunnings (X = Date, Y = Severity)
Bunnings cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Titan Company Limited
Bunnings
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.