Comparison Overview
A.P. Moller Capital

A.P. Moller Capital
Tuborg Havnevej 15, Hellerup, 2900, DK
Last Update: 08/03/2026
A.P. Moller Capital is an affiliate of A.P. Moller Holding and part of the A.P. Moller Group, founded in 2017 to manage stand-alone funds focusing on infrastructure in growth markets. Our investments support sustainable economic growth and prosperity in the markets wher...

Ackermans & van Haaren
Begijnenvest 113 Antwerp, 2000, BE
Last Update: 17/09/2026
Ackermans & van Haaren is a diversified group active in 4 core sectors: Marine Engineering & Contracting (DEME, one of the largest dredging companies in the world - CFE, a construction group with headquarters in Belgium), Private Banking (Delen Private Bank, one of the ...
Compliance Ranges Comparison

A.P. Moller Capital







Ackermans & van Haaren






Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for A.P. Moller Capital in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Ackermans & van Haaren in 2026.
Incident History - A.P. Moller Capital (X = Date, Y = Severity)
A.P. Moller Capital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ackermans & van Haaren (X = Date, Y = Severity)
Ackermans & van Haaren cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

A.P. Moller Capital

Ackermans & van Haaren
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout