Comparison Overview
Tokio Marine HCC
Tokio Marine HCC
13403 Northwest Freeway, Houston, TX, US, 77040
Last Update: 08/12/2025
Tokio Marine HCC focuses on what matters most; our people. Empowered employees deliver on commitments and look beyond profits to drive a culture of innovation and collaboration. We are diverse. We are entrepreneurial. We are forward thinkers who know risk and know our ...
Unum
1 Fountain Sq., Chattanooga, TN, US, 37402
Last Update: 03/09/2026
Since our founding in 1848, Unum has been a leader in the employee benefits business through innovation, integrity and an unwavering commitment to our customers. This simple philosophy has guided us through America’s fledgling insurance landscape and helped us become an...
Compliance Ranges Comparison
Tokio Marine HCC
Unum
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Tokio Marine HCC in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Unum in 2026.
Incident History - Tokio Marine HCC (X = Date, Y = Severity)
Tokio Marine HCC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Unum (X = Date, Y = Severity)
Unum cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Tokio Marine HCC
Unum
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