Comparison Overview
Broadridge Customer Communications

Broadridge Customer Communications
5 Dakota Dr, Lake Success, 11042, US
Last Update: 14/03/2026
Broadridge’s customer communication solutions transform how brands communicate with customers. By delivering data-driven content to the channels customers prefer, this drives better results. Discover developing communications trends, new technology and solutions to help...

Canon EMEA
4 Roundwood Avenue, Stockley Park, Uxbridge, GB, UB11 1AF
Last Update: 05/09/2026
We are Canon Europe. We are the world's best imaging company. This page represents our offices in Europe, the Middle East and Africa. Founded in 1937, the desire to continuously innovate has kept Canon at the forefront of imaging excellence throughout its 85-year histo...
Compliance Ranges Comparison

Broadridge Customer Communications







Canon EMEA






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

Broadridge Customer Communications

Canon EMEA
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