Comparison Overview
Springfield
Springfield
Avda. Llano Castellano, 51, Madrid, Madrid, 28034, ES
Last Update: 23/02/2026
De espíritu europeo, Springfield nace en 1988 como marca de casualwear ofreciendo un estilo urbano de atractivo contemporáneo y dirigida a hombres y mujeres en todo el mundo entre los 25- 35 años. Una marca para gente real y con actitud en su día a día, que está fuerte...
Bata Group
Avenue d'ouchy 61, Lausanne, 1006, CH
Last Update: 06/09/2026
The Bata Group is one of the world's leading manufacturers and retailers of quality footwear. A global concern with more than 32,000 employees, 21 production facilities, over 5,300 stores in more than 70 countries across the globe, Bata has been providing the best shoes...
Compliance Ranges Comparison
Springfield
Bata Group
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Springfield in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Bata Group in 2026.
Incident History - Springfield (X = Date, Y = Severity)
Springfield cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bata Group (X = Date, Y = Severity)
Bata Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Springfield
Bata Group
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.