Comparison Overview
Allianz Trade in The Netherlands

Allianz Trade in The Netherlands
Brabantlaan 2, 's-Hertogenbosch, 5216 TV, NL
Last Update: 18/03/2026
As the world's largest provider of credit insurance, we help companies of all sizes conduct business at home and abroad with confidence. With over 100 years of experience, a global leader in financial services, our expertise has won the trust of our global clients – ...

FactSet
43 Glover Ave, Norwalk, Connecticut, US, 06850
Last Update: 01/04/2026
FactSet creates flexible, open data and software solutions for tens of thousands of investment professionals around the world, providing instant access to financial data and analytics that investors use to make crucial decisions. For 40 years, through market changes a...
Compliance Ranges Comparison

Allianz Trade in The Netherlands







FactSet






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Allianz Trade in The Netherlands in 2026.
Incidents vs Financial Services Industry Avg (This Year)
FactSet has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Allianz Trade in The Netherlands (X = Date, Y = Severity)
Allianz Trade in The Netherlands cyber incidents detection timeline including parent company and subsidiaries.
Incident History - FactSet (X = Date, Y = Severity)
FactSet cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Allianz Trade in The Netherlands

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