Comparison Overview
Meridia
Meridia
Avenida Diagonal, 640, Barcelona, 08017, ES
Last Update: 09/02/2026
Meridia is a leading alternative investment fund manager investing in private markets in Spain. Partner of reference for some of the world’s largest and most respected institutional investors, throughout our more than 17 years of experience and various vehicles we have ...
Ackermans & van Haaren
Begijnenvest 113 Antwerp, 2000, BE
Last Update: 04/04/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
Meridia
Ackermans & van Haaren
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Meridia in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Ackermans & van Haaren in 2026.
Incident History - Meridia (X = Date, Y = Severity)
Meridia 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
Meridia
Ackermans & van Haaren
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.