Comparison Overview
Ubiquiti
Ubiquiti
Kharkiv, UA
Last Update: 08/06/2026
Беспроводное оборудование американской компании Ubiquiti, всегда в наличии. Оптовые цены, гарантия, доставка по Украине.
Tata Communications
Tata Communications Ltd, Mumbai, 400070, IN
Last Update: 07/09/2026
Tata Communications is a digital ecosystem enabler that powers today’s fast-growing digital economy. We enable the digital transformation of enterprises globally, including 300 of the Fortune 500. We carry around 30% of the world’s internet routes and connects businesse...
Compliance Ranges Comparison
Ubiquiti
Tata Communications
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Ubiquiti has 44.75% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Tata Communications in 2026.
Incident History - Ubiquiti (X = Date, Y = Severity)
Ubiquiti cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tata Communications (X = Date, Y = Severity)
Tata Communications cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ubiquiti
Tata Communications
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.