Comparison Overview
Telefónica Public Policy

Telefónica Public Policy
Ronda de la Comunicación, Madrid, 28050, ES
Last Update: 19/02/2026
Telefonica's public policy recommendations to create an open and safe Internet for all and unleash the full potential of the digital economy.

vivo
No.283 BBK Road, Wusha, Chang'an, Dongguan, Guangdong, China, Dongguan, 523860, CN
Last Update: 10/09/2026
vivo is a technology company that creates great products based on a design-driven value, with smart devices and intelligent services as its core. The company aims to build a bridge between humans and the digital world. Through unique creativity, vivo provides users with...
Compliance Ranges Comparison

Telefónica Public Policy







vivo






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

Telefónica Public Policy

vivo
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.