Comparison Overview
Intact Public Entities

Intact Public Entities
278 Pinebush Rd, Cambridge, Ontario, N1T 1Z6, CA
Last Update: 20/01/2026
Intact Public Entities is a leader in providing specialized insurance programs, including risk management and claims services to municipal, public administration and community service organizations across Canada. Proven industry knowledge, gained through over nine deca...

Allstate
3100 Sanders Rd, Northbrook, 60062, US
Last Update: 11/09/2026
At Allstate, we're advocates for peace of mind and a good life. And that comes through in everything we do. From building innovative teams that truly understand our customers' needs, to challenging each other to develop our careers in a meaningful way, and finally to ...
Compliance Ranges Comparison

Intact Public Entities







Allstate






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

Intact Public Entities

Allstate
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