Comparison Overview
Munich Re Specialty - North America

Munich Re Specialty - North America
555 College Rd E, P.O. Box 5241, Princeton, New Jersey, US, 08540
Last Update: 20/01/2026
Munich Re Specialty combines premier specialty expertise, capabilities, and products to offer partners and customers simplified access to a wide range of specialty insurance solutions and services. With Munich Re’s renowned stability, robust financial backing, and dedic...

Mapfre
Carretera de Pozuelo, 52, Majadahonda, Community of Madrid, ES, 28220
Last Update: 02/04/2026
At Mapfre, we’ve spent more than 90 years supporting people and businesses around the world, taking care of what matters most to them. We offer insurance, financial, and service solutions that evolve with you. Our experience and commitment, combined with a constant focu...
Compliance Ranges Comparison

Munich Re Specialty - North America







Mapfre






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

Munich Re Specialty - North America

Mapfre
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.