Comparison Overview
Allianz Trade in Greece
Allianz Trade in Greece
Laodikias 16 & Nymfeou 1-3, Athens, 115 28, GR
Last Update: 13/03/2026
Το σήμα Allianz Trade είναι το εμπορικό σήμα που χρησιμοποιείται για να προσδιορίσει το εύρος των υπηρεσιών που παρέχονται από την Euler Hermes. Είμαστε ο παγκόσμιος ηγέτης στην ασφάλιση εμπορικών πιστώσεων και αναγνωρισμένος ειδικός στους τομείς των εγγυήσεων, της είσπ...
Swiss Re
Mythenquai 50/60, Zurich, 8022, CH
Last Update: 01/04/2026
The Swiss Re Group is a leading wholesale provider of reinsurance, insurance and other insurance-based forms of risk transfer. Dealing direct and working through brokers, its global client base consists of insurance companies, mid-to-large-sized corporations and public ...
Compliance Ranges Comparison
Allianz Trade in Greece
Swiss Re
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Allianz Trade in Greece in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Swiss Re in 2026.
Incident History - Allianz Trade in Greece (X = Date, Y = Severity)
Allianz Trade in Greece cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swiss Re (X = Date, Y = Severity)
Swiss Re cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Allianz Trade in Greece
Swiss Re
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: *.*.