Comparison Overview
Fubon Financial Holding Co., Ltd. 富邦金控

Fubon Financial Holding Co., Ltd. 富邦金控
No.237, Sec. 1, Jianguo S. Rd., Da’an Dist.,, Taipei City, 10657, TW
Last Update: 05/04/2026
以「成為亞洲一流的金融機構」為發展願景的富邦金控,旗下主要子公司包括富邦人壽、台北富邦銀行、富邦銀行(香港)、富邦華一銀行、富邦產險、富邦證券及富邦投信等,擁有最完整多元的金融產品與服務,經營績效耀眼,位居市場領導地位。富邦金控深耕台灣逾60年,以「正向力量 成就可能™」為品牌理念,致力以正向的力量及全方位的金融服務,支持人們追尋美好未來。 截至2025年6月底,富邦金控總資產達11兆9,021億元,為台灣總資產第二大、市值第一大金融控股公司,2025年上半年稅後淨利為513.84億元,每股盈餘(EPS) 3.49元。富邦金控已連續...

Banco Sabadell
BANCO SABADELL, Pl. Sant Roc, 20, Sabadell, Barcelona, ES, 08201
Last Update: 03/04/2026
Banco Sabadell es el cuarto grupo bancario privado español, integrado por diferentes bancos, marcas, sociedades filiales y sociedades participadas que abarcan todos los ámbitos del negocio financiero bajo un denominador común: profesionalidad y calidad. Un equipo hum...
Compliance Ranges Comparison

Fubon Financial Holding Co., Ltd. 富邦金控







Banco Sabadell






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Fubon Financial Holding Co., Ltd. 富邦金控 in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco Sabadell in 2026.
Incident History - Fubon Financial Holding Co., Ltd. 富邦金控 (X = Date, Y = Severity)
Fubon Financial Holding Co., Ltd. 富邦金控 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Sabadell (X = Date, Y = Severity)
Banco Sabadell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Fubon Financial Holding Co., Ltd. 富邦金控

Banco Sabadell
FAQ
Latest Global CVEs
A flaw has been found in sigoden aichat up to 0.30.4. This affects an unknown function of the file src/serve.rs of the component API Endpoint. This manipulation causes uncontrolled memory allocation. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was detected in rowboatlabs rowboat up to 0.9.1. The impacted element is the function request.text/req.json of the file apps/rowboat/app/api/composio/webhook/route.ts of the component Composio Webhook Endpoint. The manipulation results in denial of service. It is possible to launch the attack remotely. The exploit is now public and may be used. Upgrading to version 0.9.2 is sufficient to resolve this issue. Upgrading the affected component is recommended. The legacy Next.js app was deleted at 0.9.2 rather than patched, leaving no security control behind.
A security vulnerability has been detected in Reader Tools PDF Reader App 98.8 on Android. The affected element is the function ActSplashNew.handleDeeplink of the component File Handler. The manipulation of the argument _display_name leads to path traversal. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Windows ML CLI is a command line tool for building portable, performant, and high-quality AI models for Windows ML. Prior to 0.4.0, the src/winml/modelkit/serve/cli_api.py component exposes WinML CLI commands through a localhost HTTP API without authentication and configures the allow_origins setting as a wildcard in both src/winml/modelkit/serve/cli_api.py and src/winml/modelkit/serve/app.py. A malicious website loaded by a user can send cross-origin requests to /v1/cli/build or /v1/cli/config and set the trust_remote_code parameter to true, which is converted to the --trust-remote-code command-line flag without validation. This reaches AutoConfig.from_pretrained with trust_remote_code=True in src/winml/modelkit/loader/_autoconfig.py and imports Python code from an attacker-controlled model repository, resulting in arbitrary code execution as the server user. This issue is fixed in version 0.4.0.
fast-uri serializes the port component of a URI without validating it. When recomposing the authority, the userinfo and host components are escaped but the port is concatenated verbatim, so a port value that is not a sequence of digits can inject authority delimiters, demoting the intended host to userinfo and pointing the authority at an attacker-controlled host. Both fast-uri and Node's URL read the result back as the attacker's host with no error, so re-validating the built URI does not catch it. This affects applications that build URIs from parts and assign untrusted data to the port component through the serialize, normalize, or equal functions in their object forms. The issue affects fast-uri versions before 2.4.6, from 3.0.0 before 3.1.7, and from 4.0.0 before 4.1.4. It is fixed in 2.4.6, 3.1.7, and 4.1.4, where recomposeAuthority rejects any port that is not a digit sequence per RFC 3986.