Comparison Overview
Combat Brands LLC

Combat Brands LLC
15850 W. 108th Street, None, Lenexa, KS, US, 66219-1340
Last Update: 10/03/2026
Whether you're an amateur or professional fighter, a coach, or into combat sports for its fitness benefits, Ringside and Combat Sports International are the undisputed champion and have been for years. If you're in the fight game, you need the best gear available and tr...

DECATHLON FRANCE
4, Boulevard de Mons, Villeneuve-d'Ascq, 59650, FR
Last Update: 01/04/2026
We are the world's Largest sports retailer. Founded in 1976, in France, we have set about making the pleasure and benefit of sports available for everyone across the globe. We do that by providing world class products at extremely affordable prices for all participants,...
Compliance Ranges Comparison

Combat Brands LLC







DECATHLON FRANCE






Benchmark & Cyber Underwriting Signals
Incidents vs Sporting Goods Manufacturing Industry Avg (This Year)
No incidents recorded for Combat Brands LLC in 2026.
Incidents vs Sporting Goods Manufacturing Industry Avg (This Year)
No incidents recorded for DECATHLON FRANCE in 2026.
Incident History - Combat Brands LLC (X = Date, Y = Severity)
Combat Brands LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DECATHLON FRANCE (X = Date, Y = Severity)
DECATHLON FRANCE cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Combat Brands LLC

DECATHLON FRANCE
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.