Comparison Overview
General Indemnity Group

General Indemnity Group
303 Congress St, Boston, 02210, US
Last Update: 02/04/2026
General Indemnity Group ("GIG") is an insurance holding company founded in 2015. We specialize in acquiring and operating companies that underwrite and distribute insurance products. Our current holdings include surety insurance agencies, as well as an "A- Excellent"...

AXA XL
One Bermudiana Road, Hamilton, Bermuda, BM, HM08
Last Update: 01/04/2026
We are a leading provider of insurance and reinsurance offering innovative risk management solutions for businesses worldwide. We partner with those who move the world forward, navigating complex risks and working across diverse industries to support and empower our cli...
Compliance Ranges Comparison

General Indemnity Group







AXA XL






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

General Indemnity Group

AXA XL
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.