Comparison Overview
SN Servicing Corporation
SN Servicing Corporation
13702 Coursey Blvd, Baton Rouge, 70817, US
Last Update: 30/03/2026
Security National Master Holding Company, LLC, and its affiliated corporations, is a privately held firm that specializes in loan acquisition, servicing, and real estate investment. For 25 years, we have dedicated ourselves to providing flexible and personalized solut...
Manappuram Finance Limited
IV / 470 (old) W638A (New), Manappuram House, Thrissur, 680567, IN
Last Update: 01/04/2026
Manappuram Finance Ltd. is one of India’s largest and most trusted gold loan companies, with 4,199 branches across the length and breadth of the country. It currently has nearly Rs. 157.65 billion worth assets under management (AUM), and 20,185 employees. Promoted by S...
Compliance Ranges Comparison
SN Servicing Corporation
Manappuram Finance Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for SN Servicing Corporation in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Manappuram Finance Limited in 2026.
Incident History - SN Servicing Corporation (X = Date, Y = Severity)
SN Servicing Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Manappuram Finance Limited (X = Date, Y = Severity)
Manappuram Finance Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SN Servicing Corporation
Manappuram Finance Limited
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: *.*.