Comparison Overview
AlphaCredit
AlphaCredit
Rue Montagne du Parc, 8C, Bruxelles, 1000, BE
Last Update: 23/04/2026
Al bijna 25 jaar bieden wij krediet- en verzekeringsoplossingen aan om onze klanten en partners te begeleiden. Het is onze taak om hen op een verantwoorde en innovatieve manier de kans te bieden hun dromen te verwezenlijken en hun doelstellingen te bereiken. Tegelijk wi...
Fidelity National Financial
601 Riverside Avenue, Jacksonville, 32204, US
Last Update: 01/04/2026
Fidelity National Financial, Inc. (NYSE: FNF) is a leading provider of title insurance and transaction services to the real estate and mortgage industries. Ranked #359 on the FORTUNE 500(r) list for 2023, FNF is the nation's largest title insurance company through our t...
Compliance Ranges Comparison
AlphaCredit
Fidelity National Financial
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for AlphaCredit in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Fidelity National Financial in 2026.
Incident History - AlphaCredit (X = Date, Y = Severity)
AlphaCredit cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fidelity National Financial (X = Date, Y = Severity)
Fidelity National Financial cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AlphaCredit
Fidelity National Financial
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: *.*.