Comparison Overview
Leisure Lakes Bikes
Leisure Lakes Bikes
124 Rochdale Road, Bury, Lancashire, BL9 7AY, GB
Last Update: 14/01/2026
Leisure Lakes Bikes are a family run business established over 31 years ago by four brothers with a great passion for the outdoors. We now have two generations of the 'Noy' family working throughout different areas of the company and we are excited to expand to our eigh...
Pick n Pay
PnP Office Park, Kenilworth, 7708, ZA
Last Update: 14/09/2026
Welcome to Pick n Pay, where family values and customer-centricity converge to create an unparalleled shopping experience. Since 1967, when the visionary Raymond Ackerman championed the cause of consumers by acquiring the first few stores, the Ackerman family's dedicati...
Compliance Ranges Comparison
Leisure Lakes Bikes
Pick n Pay
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Leisure Lakes Bikes in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Pick n Pay in 2026.
Incident History - Leisure Lakes Bikes (X = Date, Y = Severity)
Leisure Lakes Bikes cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pick n Pay (X = Date, Y = Severity)
Pick n Pay cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Leisure Lakes Bikes
Pick n Pay
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.