Comparison Overview
GPI Holding - Vienna Insurance Group
GPI Holding - Vienna Insurance Group
88/15 Bochorishvili, Tbilisi, Tbilisi, 0161, GE
Last Update: 15/02/2026
GPI holding is not just an insurance company. We offer our employees rewarding careers in a financially stable, progressive and supportive work environment. GPI Holding is a place with more than 400 active and innovative people specializing in sales, customer service, i...
MetLife
200 Park Ave, New York, NY, US, 10166
Last Update: 04/09/2026
We live in a time of unprecedented change. A time when economies, regulations, and social safety nets are all in flux. Customers around the globe have told us they’re overwhelmed by the pace of change and are looking for a trusted partner to help them manage life’s twi...
Compliance Ranges Comparison
GPI Holding - Vienna Insurance Group
MetLife
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for GPI Holding - Vienna Insurance Group in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for MetLife in 2026.
Incident History - GPI Holding - Vienna Insurance Group (X = Date, Y = Severity)
GPI Holding - Vienna Insurance Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MetLife (X = Date, Y = Severity)
MetLife cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
GPI Holding - Vienna Insurance Group
MetLife
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