Comparison Overview
Telefónica

Telefónica
Spain, Madrid, 28050, ES
Last Update: 12/05/2026
Telefónica is today one of the largest telecommunications companies in the world in terms of market capitalisation and number of customers. We have the best infrastructure, as well as an innovative range of digital and data services; therefore, we are favorably position...

PTCL.Official
Block-E, Sector G-8/4, Islamabad, 44000, PK
Last Update: 02/04/2026
𝗩𝗶𝘀𝗶𝗼𝗻: To be the leading and most admired Telecom and ICT provider in and for Pakistan. 𝐌𝐢𝐬𝐬𝐢𝐨𝐧: To be the partner of choice for our customers, to develop our people and to deliver value to our shareholders. 𝗖𝗼𝗿𝗽𝗼𝗿𝗮𝘁𝗲 𝗩𝗮𝗹𝘂𝗲𝘀: Be resilie...
Compliance Ranges Comparison

Telefónica







PTCL.Official






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

Telefónica

PTCL.Official
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.