Comparison Overview
T-Systems Nordic

T-Systems Nordic
Dampfærgevej 21, København Ø, Copenhagen, 2100, DK
Last Update: 22/04/2026
We are driven to help companies successfully digitise their business – today and in the future. That is why we’ve adapted our global portfolio in the local markets across Northern Europe, to become a trusted partner for our customers through delivering innovative, agile...

Apex Systems
4400 Cox Road, Suite 200, Glen Allen, VA, US, 23060
Last Update: 13/09/2026
Apex Systems is a leading global technology services firm that incorporates industry insights and experience to deliver solutions that fulfill our clients’ digital visions. We offer a continuum of services, specializing in strategy, transformation, and managed services ...
Compliance Ranges Comparison

T-Systems Nordic







Apex Systems






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for T-Systems Nordic in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Apex Systems in 2026.
Incident History - T-Systems Nordic (X = Date, Y = Severity)
T-Systems Nordic cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Apex Systems (X = Date, Y = Severity)
Apex Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

T-Systems Nordic

Apex Systems
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