Comparison Overview
Futurecom Systems Group ULC

Futurecom Systems Group ULC
3277 Langstaff Road, Concord, L4K 5P8, CA
Last Update: 27/01/2026
Futurecom was acquired by Motorola Solutions in 2022 and is now part of its ecosystem of safety and security technologies. Futurecom is a leading provider of radio coverage extension solutions for public safety agencies. It designs & manufactures in-vehicle, fixed and...

Spectrum
Stamford , 06901, US
Last Update: 02/06/2026
Spectrum is a suite of advanced communications services offered by Charter Communications, Inc. (NASDAQ:CHTR), a leading broadband connectivity company available to more than 57 million homes and small to large businesses across 41 states. Founded in 1993, Charter has e...
Compliance Ranges Comparison

Futurecom Systems Group ULC







Spectrum






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Futurecom Systems Group ULC in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
Spectrum has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Futurecom Systems Group ULC (X = Date, Y = Severity)
Futurecom Systems Group ULC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Spectrum (X = Date, Y = Severity)
Spectrum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Futurecom Systems Group ULC

Spectrum
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.