Comparison Overview
Wemanity Reply Lille
Wemanity Reply Lille
57-59 rue National,, Lille, Hauts-de-France, FR, 59800
Last Update: 14/05/2026
Wemanity Reply is a consulting and delivery firm specialized in technological, organizational, and cultural transformation. We help organizations turn strategy into execution by combining artificial intelligence, modern technology, and human ingenuity to create sustaina...
VINCI Energies
2169, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 14/09/2026
In a world undergoing constant change, VINCI Energies contributes to the environmental transition by helping bring about major trends in the digital landscape and energy sector. VINCI Energies’ teams roll out technologies and integrate customised multi-technical solutio...
Compliance Ranges Comparison
Wemanity Reply Lille
VINCI Energies
Benchmark & Cyber Underwriting Signals
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for Wemanity Reply Lille in 2026.
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for VINCI Energies in 2026.
Incident History - Wemanity Reply Lille (X = Date, Y = Severity)
Wemanity Reply Lille cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VINCI Energies (X = Date, Y = Severity)
VINCI Energies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Wemanity Reply Lille
VINCI Energies
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