Comparison Overview
Kent Building Supplies
Kent Building Supplies
300 Union Street, Saint John, E2L 4G7, CA
Last Update: 02/04/2026
Your Future with Kent starts here! Do you enjoy working as part of a team? From cashiers to store managers to marketing and purchasing, there are a wide variety of careers available. Whether you have years of experience or are just starting out, whether you want to pro...
Specsavers
La Villiaize, St Andrews, Global, GB, GY6 8YP
Last Update: 14/09/2026
Specsavers began 40 years ago with the vision of two optometrists, Doug and Mary Perkins, who set out to provide best-value eyecare to everybody. Their passion for optometry has led Specsavers to become the largest privately-owned optical group in the world, deliverin...
Compliance Ranges Comparison
Kent Building Supplies
Specsavers
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Kent Building Supplies in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Specsavers in 2026.
Incident History - Kent Building Supplies (X = Date, Y = Severity)
Kent Building Supplies cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Specsavers (X = Date, Y = Severity)
Specsavers cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Kent Building Supplies
Specsavers
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.