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

Ericsson
Torshamnsgatan 21, Kista, Stockholm, SE
Last Update: 02/04/2026
The future of mobile isn’t on the horizon, it’s happening now. At Ericsson, we’re building the foundation for an open network ecosystem where industries, developers, and enterprises thrive. The convergence of 5G, AI, cloud, and network APIs isn’t just a technological s...
Compliance Ranges Comparison

Bouygues Telecom Pro







Ericsson






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)
Ericsson has 175.23% more incidents than the average of all companies with at least one recorded incident.
Incident History - Bouygues Telecom Pro (X = Date, Y = Severity)
Bouygues Telecom Pro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ericsson (X = Date, Y = Severity)
Ericsson cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bouygues Telecom Pro

Ericsson
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.