Comparison Overview
T-Systems México
T-Systems México
Puebla, Puebla, MX, 72480
Last Update: 04/01/2026
T-Systems is a strategic partner for digital transformation of companies and institutions with a unique capacity in Mexico to offer competitive solutions according to the challenges and objectives of each organization. It is part of the German group Deutsche Telekom AG,...
Allianz Technology
Dieselstraße 8, Unterföhring, Bavaria, DE, 85774
Last Update: 13/09/2026
With its headquarters in Munich, Germany, Allianz Technology is Allianz's global IT service provider and delivers IT solutions that drive the group's digitalization. With more than 11,000 employees in more than 20 countries around the world, Allianz Technology is tasked...
Compliance Ranges Comparison
T-Systems México
Allianz Technology
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for T-Systems México in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Allianz Technology in 2026.
Incident History - T-Systems México (X = Date, Y = Severity)
T-Systems México cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Allianz Technology (X = Date, Y = Severity)
Allianz Technology cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
T-Systems México
Allianz Technology
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