Comparison Overview
VIVO

VIVO
Avenida Luis Carlos Berrini, São Paulo, 04571-000 , BR
Last Update: 19/02/2026
Vivo é a marca comercial da Telefônica no Brasil, a maior operadora de telecomunicações do país. Conecte-se você também com a gente!

Nokia
Karakaari 7, Espoo, 02610, FI
Last Update: 06/09/2026
Nokia is a global leader in connectivity for the AI era. With expertise across fixed, mobile, and transport networks, powered by the innovation of Nokia Bell Labs, we’re advancing connectivity to secure a brighter world. Advanced connectivity is key to enable the oppor...
Compliance Ranges Comparison

VIVO







Nokia






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

VIVO

Nokia
FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.