Comparison Overview
Poundland & Dealz
Poundland & Dealz
Midland Road, Walsall, WV1 3TX, GB
Last Update: 10/03/2026
From one store in Burton-upon-Trent in 1990 to more than 650 across the UK and the Republic of Ireland today, Poundland & Dealz has developed a reputation for offering top brands and quality own-brand products at an amazing value. We sell everything from food and drink ...
Pilot Flying J
5508 Lonas Rd., Knoxville, 37909, US
Last Update: 05/09/2026
Company Overview Headquartered in Knoxville, Tennessee, Pilot Flying J is the largest operator of travel centers in North America with more than 750 locations throughout the United States and Canada and employs more than 24,000 Team Members. Pilot Flying J services over...
Compliance Ranges Comparison
Poundland & Dealz
Pilot Flying J
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Poundland & Dealz in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Pilot Flying J in 2026.
Incident History - Poundland & Dealz (X = Date, Y = Severity)
Poundland & Dealz cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pilot Flying J (X = Date, Y = Severity)
Pilot Flying J cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Poundland & Dealz
Pilot Flying J
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.