Comparison Overview
LSN Assurances
LSN Assurances
39, Rue Mstislav Rostropovitch, Paris, 75017, FR
Last Update: 02/04/2026
Fondée il y a 60 ans, LSN Assurances propose aujourd'hui avec ses filiales (LSN Ré, Neotech) une large gamme d’expertises en assurance de responsabilité et en assurance et réassurance de biens et de personnes. Notre savoir-faire s'adresse aux professions réglementées do...
Seguros SURA
Edificio Suramericana Carrera 64 B 49 A 30, Medellín, Antioquia, CO
Last Update: 03/04/2026
SURA es una compañía que integra en diferentes empresas soluciones en seguros y seguridad social. Su marca se presenta a los clientes como Seguros SURA, ARL SURA y EPS SURA. Existen otras marcas y empresas, especialmente de prestación de servicios, que hacen parte de la...
Compliance Ranges Comparison
LSN Assurances
Seguros SURA
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for LSN Assurances in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Seguros SURA in 2026.
Incident History - LSN Assurances (X = Date, Y = Severity)
LSN Assurances cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Seguros SURA (X = Date, Y = Severity)
Seguros SURA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
LSN Assurances
Seguros SURA
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: *.*.