Comparison Overview
Groupe Burrus
Groupe Burrus
-, CH
Last Update: 02/04/2026
Since 1923, the Groupe Burrus has been formed by organic growth and by acquisitions of companies in the fields of insurance, brokerage and finance. Composed of numerous companies and with nearly 1,400 employees, the Groupe Burrus is a solid financial group with lasting...
Vienna Insurance Group (VIG)
Schottenring 30, Vienna, 1010, AT
Last Update: 03/04/2026
Vienna Insurance Group (VIG) is the leading insurance group in the entire Central and Eastern European (CEE) region. More than 50 insurance companies and pension funds in 30 countries form a Group with a long-standing tradition, strong brands and close customer relation...
Compliance Ranges Comparison
Groupe Burrus
Vienna Insurance Group (VIG)
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Groupe Burrus in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Vienna Insurance Group (VIG) in 2026.
Incident History - Groupe Burrus (X = Date, Y = Severity)
Groupe Burrus cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vienna Insurance Group (VIG) (X = Date, Y = Severity)
Vienna Insurance Group (VIG) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Groupe Burrus
Vienna Insurance Group (VIG)
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: *.*.