Comparison Overview
Grupo Pernambucanas
Grupo Pernambucanas
Rua da Consolação 2411, Sao Paulo, BR
Last Update: 03/04/2026
Somos a companhia que veste a vida dos brasileiros. O Grupo Pernambucanas é a marca que leva estilo, calor e facilidade para os brasileiros desde que nasceu. Que abre as portas para um universo de possibilidades que vão muito além das araras. É a marca que tem o olh...
DICK'S Sporting Goods
345 Court Street, Coraopolis, PA, US, 15108
Last Update: 02/04/2026
YOU LIVE AND BREATHE SPORTS. SO DO WE. In work and in life. On the field, the court or the ice. Nothing wins like a commitment to excellence; to your team and your goals. At DICK’S Sporting Goods, it’s this kind of thinking that inspires our mission. Our culture is t...
Compliance Ranges Comparison
Grupo Pernambucanas
DICK'S Sporting Goods
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Grupo Pernambucanas in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for DICK'S Sporting Goods in 2026.
Incident History - Grupo Pernambucanas (X = Date, Y = Severity)
Grupo Pernambucanas cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DICK'S Sporting Goods (X = Date, Y = Severity)
DICK'S Sporting Goods cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Grupo Pernambucanas
DICK'S Sporting Goods
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.