Comparison Overview
Caleres, Inc.

Caleres, Inc.
8300 Maryland Avenue, St. Louis, Missouri, US, 63105
Last Update: 12/03/2026
Caleres is the home of today’s most coveted footwear brands around the world and represents a diverse portfolio spanning all of life’s styles and experiences. Every shoe tells a story and Caleres has the perfect fit for every one of them. Caleres’ brands live in all cha...

Tailored Brands, Inc.
6380 Rogerdale Rd, Houston, 77072, US
Last Update: 08/09/2026
Our Purpose: We help people love the way they look and feel for their most important moments. Our Values: • Customer-First - We put customers at the center of every decision • Win Together - We rally together to achieve common goals • Better Every Day - We strive for e...
Compliance Ranges Comparison

Caleres, Inc.







Tailored Brands, Inc.






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Caleres, Inc. in 2026.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for Tailored Brands, Inc. in 2026.
Incident History - Caleres, Inc. (X = Date, Y = Severity)
Caleres, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tailored Brands, Inc. (X = Date, Y = Severity)
Tailored Brands, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Caleres, Inc.

Tailored Brands, Inc.
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.