Comparison Overview
Bouygues Telecom Pro

Bouygues Telecom Pro
13, Avenue du Maréchal Juin, Meudon, 92360, FR
Last Update: 20/04/2026
Nos experts accompagnent les pros, TPE et PME et facilitent la vie des professionnels en concevant des offres simples et packagées pour communiquer efficacement et sécuriser leurs activités. Acteur majeur de la démocratisation de la Fibre Entreprise en France et précur...

Cox Communications
6205 Peachtree Dunwoody Road, Atlanta, 30328, US
Last Update: 01/04/2026
Cox Communications is committed to creating more moments of real human connection. We bring people closer to family and friends through technology that’s inspired by a culture that puts people first, and we’re always working to improve life in the communities we serve. ...
Compliance Ranges Comparison

Bouygues Telecom Pro







Cox Communications






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

Bouygues Telecom Pro

Cox Communications
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.