Comparison Overview
OMNIASIG Vienna Insurance Group

OMNIASIG Vienna Insurance Group
Aleea Alexandru 51, București, Romania, undefined, RO
Last Update: 27/11/2025
Din 1995, OMNIASIG 💚 continuă să facă din PERFORMANȚĂ o TRADIȚIE. Pentru noi, dorința permanentă de a atinge PERFORMANȚA este motivul pentru care acționăm întotdeauna cu PASIUNE și PROFESIONALISM. Pe parcursul tuturor acestor ani, INTEGRITATEA, RESPECTUL, ÎNCREDEREA ...

Swiss Re
Mythenquai 50/60, Zurich, 8022, CH
Last Update: 01/04/2026
The Swiss Re Group is a leading wholesale provider of reinsurance, insurance and other insurance-based forms of risk transfer. Dealing direct and working through brokers, its global client base consists of insurance companies, mid-to-large-sized corporations and public ...
Compliance Ranges Comparison

OMNIASIG Vienna Insurance Group







Swiss Re






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

OMNIASIG Vienna Insurance Group

Swiss Re
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.