Comparison Overview
ClientPay
ClientPay
3700 N Capital of Texas Hwy, Austin, Texas, 78746, US
Last Update: 05/05/2026
ClientPay is a simple, web-based solution designed specifically for architecture, engineering, design, and construction professionals. ClientPay gives you the power to securely accept credit card and eCheck payments from anywhere—in your office, online, even at a projec...
Mahindra Finance
Dr. G.M. Bhosale Marg, P.K. Kurne Chowk, Worli, Mumbai, 400018, IN
Last Update: 02/04/2026
Mahindra & Mahindra Financial Services Limited (Mahindra Finance), part of the Mahindra Group, is one of India's leading non-banking finance companies. Focused on the rural and semi-urban sector, the Company has over 10 million customers and has an AUM of over USD 11 B...
Compliance Ranges Comparison
ClientPay
Mahindra Finance
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for ClientPay in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Mahindra Finance in 2026.
Incident History - ClientPay (X = Date, Y = Severity)
ClientPay cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mahindra Finance (X = Date, Y = Severity)
Mahindra Finance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ClientPay
Mahindra Finance
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: *.*.