Comparison Overview
AXA COLPATRIA
AXA COLPATRIA
Carrera 7 # 24 - 89 Mezzanine Local 202 (Ahorro y Seguros), Bogotá, CO
Last Update: 13/03/2026
AXA COLPATRIA, una compañía con 70 años de experiencia en el mercado colombiano, con el respaldo de AXA, la marca de seguros número 1 en el mundo, la 3ra marca de servicios financieros y la 42 con más reconocimiento a nivel mundial. Contamos con un amplio portafolio de...
Discover
2500 Lake Cook Road, Riverwoods, IL, US, 60015
Last Update: 01/04/2026
Discover® is now part of Capital One. Together, we’ll continue to deliver exceptional financial products and experiences, drive innovation, and serve customers. Find the latest updates at https://capitalonediscover.com. Discover is one of the most recognized brands in ...
Compliance Ranges Comparison
AXA COLPATRIA
Discover
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for AXA COLPATRIA in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Discover in 2026.
Incident History - AXA COLPATRIA (X = Date, Y = Severity)
AXA COLPATRIA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Discover (X = Date, Y = Severity)
Discover cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AXA COLPATRIA
Discover
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: *.*.