Comparison Overview
Compensa Life Vienna Insurance Group SE Latvian Branch

Compensa Life Vienna Insurance Group SE Latvian Branch
Vienības gatve 87h, Riga, LV-1004, LV
Last Update: 21/01/2026
Vienna Insurance Group is one of the traditional European insurance groups with almost 200 years of experience. The company has its roots in Austria, in its arts and cultural capital Vienna. The values of the old European city continue to live in Compensa today – the ar...

Gallagher
2850 Golf Road, Rolling Meadows, 60008, US
Last Update: 10/06/2026
Gallagher, a global insurance brokerage, risk management, and consulting firm, serves communities around the globe, helping clients address risk, protecting assets, and recovering from losses. The products and services we provide keep businesses and institutions running...
Compliance Ranges Comparison

Compensa Life Vienna Insurance Group SE Latvian Branch







Gallagher






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Compensa Life Vienna Insurance Group SE Latvian Branch in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Gallagher in 2026.
Incident History - Compensa Life Vienna Insurance Group SE Latvian Branch (X = Date, Y = Severity)
Compensa Life Vienna Insurance Group SE Latvian Branch cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Gallagher (X = Date, Y = Severity)
Gallagher cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Compensa Life Vienna Insurance Group SE Latvian Branch

Gallagher
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.