Comparison Overview
Total Cyber-Sec

Total Cyber-Sec
Camino a Santa Teresa 187C, 14010, Parques del Pedregal, CDMX, 14000, MX
Last Update: 22/03/2026
Somos una empresa de Grupo Salinas con un equipo de profesionales en Seguridad de la Información con más de 15 años de experiencia que nos respalda en los sectores: financieros, retail, telecomunicaciones, entre otros. Nuestra misión es brindar a nuestros clientes solu...

Kyndryl
New York City, US
Last Update: 11/09/2026
We have the world’s best talent that design, run, and manage the most advanced and reliable technology infrastructure each day. Together, we think holistically about the health of these vital technology ecosystems. We are a focused, independent company that builds on o...
Compliance Ranges Comparison

Total Cyber-Sec







Kyndryl






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Total Cyber-Sec in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Kyndryl has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Total Cyber-Sec (X = Date, Y = Severity)
Total Cyber-Sec cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kyndryl (X = Date, Y = Severity)
Kyndryl cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Total Cyber-Sec

Kyndryl
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