Comparison Overview
Peak Re
Peak Re
NO.8 AUSTIN ROAD WEST, Hong Kong, undefined, undefined, HK
Last Update: 19/03/2026
Peak Reinsurance Company Limited (“Peak Re” or the “Company”) is a Hong Kong-based global reinsurance company. Since commencing operations in 2012, the Company has grown steadily to rank 27th among global reinsurance groups in terms of net reinsurance premiums written. ...
Liberty Mutual Insurance
175 Berkeley Street, Boston, 02116, US
Last Update: 13/09/2026
At Liberty Mutual, we believe progress happens when people feel secure. For more than 110 years we have helped people and businesses embrace today and confidently pursue tomorrow by providing protection for the unexpected and delivering it with care. A Fortune 100 c...
Compliance Ranges Comparison
Peak Re
Liberty Mutual Insurance
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Peak Re in 2026.
Incidents vs Insurance Industry Avg (This Year)
Liberty Mutual Insurance has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Peak Re (X = Date, Y = Severity)
Peak Re cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Liberty Mutual Insurance (X = Date, Y = Severity)
Liberty Mutual Insurance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Peak Re
Liberty Mutual Insurance
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