Comparison Overview
Comtel Innovation - International

Comtel Innovation - International
Via Cornaggia 58 - Cinisello Balsamo, Milano, Milano, IT, 20092
Last Update: 03/04/2026
Following the acquisition of NEC Corporation's Unified Communication division for the EMEA area by COMTEL Italia, NEC ITALIA is renamed COMTEL Innovation, and NEC NEDERLAND becomes COMTEL International. This marks the creation of a broad, integrated, and future-oriente...

Openreach
6 Gracechurch Street, London, EC3V 0AT, GB
Last Update: 01/04/2026
We’re the people who make the net work. As the nation’s largest wholesale broadband network, we’re rolling out Ultrafast Full Fibre broadband across the UK. It’s our fastest and most reliable broadband yet, and we’re well on our way to making it available to 25m homes ...
Compliance Ranges Comparison

Comtel Innovation - International







Openreach






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

Comtel Innovation - International

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