Comparison Overview
TD SYNNEX Netherlands
TD SYNNEX Netherlands
Tolnasingel 2, Bodegraven, Zuid Holland, 2411 PV, NL
Last Update: 07/03/2026
Als een innovatieve partner zien wij het als onze taak ervoor te zorgen dat onze ruim 150.000 klanten in meer dan 100 landen de waarde van hun technologische investeringen maximaliseren, bedrijfsresultaten behalen en groeimogelijkheden ontsluiten. De hoofdkantoren van ...
Inetum
5, Rue Touzet Gaillard, St.-Ouen, Île-de-France, FR, 93400
Last Update: 07/09/2026
Inetum is a European leader in digital services. Inetum’s team of 27,000 consultants and specialists strive every day to make a digital impact for businesses, public sector entities and society. Inetum’s solutions aim at contributing to its clients’ performance and inno...
Compliance Ranges Comparison
TD SYNNEX Netherlands
Inetum
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for TD SYNNEX Netherlands in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Inetum in 2026.
Incident History - TD SYNNEX Netherlands (X = Date, Y = Severity)
TD SYNNEX Netherlands cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Inetum (X = Date, Y = Severity)
Inetum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TD SYNNEX Netherlands
Inetum
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