Comparison Overview
Garanti BBVA Portföy
Garanti BBVA Portföy
Nisbetiye Mh, Çiftçi Towers Kule, Barbaros Blv. No: 96 D:1/ Kat 4, 34340 Beşiktaş/İstanbul, İstanbul, Beşiktaş, 34340, TR
Last Update: 29/11/2025
Garanti BBVA Asset Management, being Turkey's first Asset Management Company established in 05.06.1997, is 100% Garanti BBVA subsidiary. Garanti BBVA Asset Management commencing with its activities in 1997 as the first and pioneering company of its sector serves its cu...
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
Garanti BBVA Portföy
Sabanci Holding
Benchmark & Cyber Underwriting Signals
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Garanti BBVA Portföy in 2026.
Incidents vs Investment Management Industry Avg (This Year)
No incidents recorded for Sabanci Holding in 2026.
Incident History - Garanti BBVA Portföy (X = Date, Y = Severity)
Garanti BBVA Portföy 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
Garanti BBVA Portföy
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: *.*.