Comparison Overview
Maybank
Maybank
100 Jalan Tun Perak, Kuala Lumpur, Wilayah Persekutuan, MY, 50050
Last Update: 02/04/2026
Maybank Group is the leading financial services provider in Malaysia catering to the needs of consumers, investors, entrepreneurs, non-profit organisations and corporations. The Group, which has expanded internationally, has the largest network among Malaysian banks of ...
PT Bank SMBC Indonesia Tbk
Menara SMBC-Jl. Dr. Ide Anak Agung Gde Agung Kav. 5.5 – 5.6, Jakarta 12950, Jakarta Selatan, 12950, ID
Last Update: 01/04/2026
With a renewed vision for growth and innovation, we rebranded as PT Bank SMBC Indonesia Tbk (SMBC Indonesia) in 2024, formerly known as PT Bank BTPN Tbk. This rebranding reflects our response to the dynamic changes, allowing us to consolidate our strengths and deliver e...
Compliance Ranges Comparison
Maybank
PT Bank SMBC Indonesia Tbk
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Maybank in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for PT Bank SMBC Indonesia Tbk in 2026.
Incident History - Maybank (X = Date, Y = Severity)
Maybank cyber incidents detection timeline including parent company and subsidiaries.
Incident History - PT Bank SMBC Indonesia Tbk (X = Date, Y = Severity)
PT Bank SMBC Indonesia Tbk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Maybank
PT Bank SMBC Indonesia Tbk
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: *.*.