Comparison Overview
Telenor Towers

Telenor Towers
Snarøyveien 30, Fornebu, Viken, 1360, NO
Last Update: 29/12/2025
In 2023, Telenor Infra Norway, Telenor Tower Sweden and DNA Tower Finland united into Telenor Towers, the largest tower company in the Nordics. With a history spanning over a century in the infrastructure industry, we have been at the forefront of advancing modern in...

Telkomsel
Telkomsel Smart Office - Kompleks Telkom Landmark Tower, Jakarta Selatan, 12710, ID
Last Update: 02/04/2026
Connecting Nation. Accelerating Indonesia's Future. As Indonesia's leading digital telecommunications company, Telkomsel is committed to building a connected, competitive, and future-ready society. For over 29 years, we've empowered individuals, homes, and businesses w...
Compliance Ranges Comparison

Telenor Towers







Telkomsel






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telenor Towers in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telkomsel in 2026.
Incident History - Telenor Towers (X = Date, Y = Severity)
Telenor Towers cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Telkomsel (X = Date, Y = Severity)
Telkomsel cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Telenor Towers

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