Comparison Overview
Bouygues Telecom Business

Bouygues Telecom Business
13 avenue du Maréchal Juin, Meudon-la-Forêt, 92, FR
Last Update: 28/03/2026
Notre métier ? Vous proposer des solutions adaptées à votre activité : Téléphonie Fixe et Mobile, Internet et Réseaux, Services et prestations. Depuis 1997, Bouygues Telecom Entreprises s’engage à vous proposer des solutions de communications conçues pour vous permet...

Lumen Technologies
Monroe, Louisiana , US, 71203
Last Update: 15/09/2026
Lumen connects the world. We digitally connect people, data and applications – quickly, securely and effortlessly. Everything we do at Lumen takes advantage of our network strength. From metro connectivity to long-haul data transport to our edge cloud, security, and man...
Compliance Ranges Comparison

Bouygues Telecom Business







Lumen Technologies






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

Bouygues Telecom Business

Lumen Technologies
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout