Comparison Overview
Bradesco Prime

Bradesco Prime
Cidade de Deus, s/nº, Osasco, São Paulo, 060029900, BR
Last Update: 21/01/2026
Somos o Bradesco Prime. Atuamos no segmento de alta renda em todo o território nacional, com um modelo de relacionamento completo que se adapta ao perfil e à necessidade de cada cliente com soluções completas para todos os momentos. Temos um modelo de assessoria fina...

alinma
King Fahad Road - Alanoud Northern Tower, PO Box 66674, Riyadh, SA, 11586
Last Update: 02/04/2026
Alinma Bank is a Saudi joint stock company formed in accordance with Royal Decree No. M/15 dated 28/2/1427H (28/3/2006) and Ministerial Resolution No. 42 dated 27/2/1427H (27/3/2006). The share capital of Alinma Bank is SAR 20 billion consisting of 1.5 billion shares wi...
Compliance Ranges Comparison

Bradesco Prime







alinma






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Bradesco Prime in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for alinma in 2026.
Incident History - Bradesco Prime (X = Date, Y = Severity)
Bradesco Prime cyber incidents detection timeline including parent company and subsidiaries.
Incident History - alinma (X = Date, Y = Severity)
alinma cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bradesco Prime

alinma
FAQ
Latest Global CVEs
Improper access control in Microsoft Edge for Android allows an unauthorized attacker to bypass a security feature over a network.
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. Affected is the function GatewayStreamConsumer._filter_and_accumulate of the file gateway/stream_consumer.py of the component Streaming Reasoning Tag Filter. The manipulation leads to improper handling of case sensitivity. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project decided to not implement a dedicated fix: "[T]he analysis and the fix are both sound. It just lands below the bar for the maintenance cost of a duplicated scrub path."
- https://gist.github.com/YLChen-007/2229e5505bcbb3e15a7ae8fba4c4be37
- https://github.com/NousResearch/hermes-agent/
- https://github.com/NousResearch/hermes-agent/issues/27288
- https://github.com/NousResearch/hermes-agent/pull/28631#issuecomment-4622188016
- https://vuldb.com/cve/CVE-2026-14617
- https://vuldb.com/submit/844654
- https://vuldb.com/vuln/376134
- https://vuldb.com/vuln/376134/cti
Insufficient ui warning of dangerous operations in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Relative path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.