Comparison Overview
Heimtextil
Heimtextil
Ludwig-Erhard-Anlage 1, Frankfurt am Main, DE
Last Update: 12/12/2025
Heimtextil in Frankfurt am Main/Germany is the biggest international trade fair for home and contract textiles and the global benchmark for quality design textiles of innovative functionality. As the first trade fair of the year, Heimtextil, which is held on four fair d...
Shaw Industries
616 East Walnut Ave, Dalton, 30720, US
Last Update: 30/03/2026
Shaw Industries Group, Inc. is a leader in flooring and other surface solutions designed for residential housing, commercial spaces and outdoor environments. Leveraging strengths in design, innovation and operational excellence, the company takes a people-centered, cust...
Compliance Ranges Comparison
Heimtextil
Shaw Industries
Benchmark & Cyber Underwriting Signals
Incidents vs Textile Manufacturing Industry Avg (This Year)
No incidents recorded for Heimtextil in 2026.
Incidents vs Textile Manufacturing Industry Avg (This Year)
No incidents recorded for Shaw Industries in 2026.
Incident History - Heimtextil (X = Date, Y = Severity)
Heimtextil cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Shaw Industries (X = Date, Y = Severity)
Shaw Industries cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Heimtextil
Shaw Industries
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.