Comparison Overview
ARX Investimentos
ARX Investimentos
Avenida Borges de Medeiros 633, Rio de Janeiro, 22430-041, BR
Last Update: 12/03/2026
A ARX Investimentos foi fundada em 2001 e é controlada, desde 2008, pelo grupo BNY, uma das mais tradicionais instituições financeiras do mundo. A ARX é uma das gestoras mais experientes e confiáveis do Brasil e possui total independência no país, ao mesmo tempo que se...
Sabanci Holding
Sabancı Center 4.Levent, İstanbul, 34330, TR
Last Update: 04/04/2026
Sabancı Holding is one of Turkey’s leading conglomerate, engaged in a wide variety of business activities through its subsidiaries and affiliates, mainly in the banking, financial services, energy, industrials, building materials and retail sectors. Our Group companies ...
Compliance Ranges Comparison
ARX Investimentos
Sabanci Holding
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for ARX Investimentos in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Sabanci Holding in 2026.
Incident History - ARX Investimentos (X = Date, Y = Severity)
ARX Investimentos cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sabanci Holding (X = Date, Y = Severity)
Sabanci Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ARX Investimentos
Sabanci Holding
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: *.*.