Comparison Overview
AIA Taiwan

AIA Taiwan
N/A
Last Update: 22/04/2026
友邦保險控股有限公司及其附屬公司(統稱「友邦保險」或「本集團」)是最大的泛亞地區獨立上市人壽保險集團,覆蓋18個市場,包括在中國內地、香港特別行政區、泰國、新加坡、馬來西亞、澳洲、柬埔寨、印尼、緬甸、菲律賓、南韓、斯里蘭卡、中國台灣、越南、汶萊、澳門特別行政區和新西蘭擁有全資的分公司及附屬公司,以及印度合資公司的49%權益。 友邦保險今日的業務成就可追溯至1919年逾一個世紀前於上海的發源地。按壽險保費計算,集團在亞洲(日本除外)領先同業,並於大部分市場穩佔領導地位。截至2020年12月31日,集團總資產值為3,260億美元。 友...

Lockton
Global, US
Last Update: 04/09/2026
What makes Lockton stand apart is also what makes us better: independence. Our private ownership empowers our 13,100+ Associates doing business in over 140+ countries to focus solely on clients' risk and insurance needs. With expertise that reaches around the globe, we ...
Compliance Ranges Comparison

AIA Taiwan







Lockton






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

AIA Taiwan

Lockton
FAQ
Latest Global CVEs
A flaw has been found in OpenClaw up to 2026.9.5. Affected is the function createCanvasHostHandler of the file extensions/canvas/src/host/server.ts of the component Canvas Host Route. Executing a manipulation can lead to denial of service. The attack can be launched remotely. The exploit has been published and may be used. Fix suggestion's "streaming/size-limit" was never shipped - latest 2026.9.5 still buffers the whole file via readFile() (src/canvas/serve.runtime.ts:17,114), unlike the sibling WS path which caps at 64KB. The vendor was contacted early about this disclosure.
A security vulnerability has been detected in DLR-RM stable-baselines3 up to 2.9.0. This affects the function PPO.load/load_replay_buffer/VecNormalize.load of the file save_util.py. Such manipulation leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. In v2.9.0 the PyTorch tensor load path is hardened (weights_only=True), but that hardening was later reverted on master via PR #1913 "Hotfix: revert loading with weights_only=True" [blocked] to fix PyTorch 1.13 compat - so even the one "safe" path is inconsistent across versions. #2281 was closed as a duplicate of #1831 since both are unsafe pickle deserialization - but #1831's fix (PR #41) only gated the Hugging Face Hub loader in the separate huggingface_sb3 package. This finding covers the core stable_baselines3 load APIs (PPO.load, load_replay_buffer, VecNormalize.load), which have no safe mode or gate and remained exploitable in v2.9.0 until the outstanding hardening (PR #2264) ships.
A vulnerability was detected in dmlc dgl up to 2.1.0. This impacts the function load_info/_read_torch_data of the file utils.py. Performing a manipulation of the argument path results in deserialization. The attack can be initiated remotely. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in piskvorky gensim up to 4.4.0. The impacted element is the function Load of the file gensim/utils.py of the component Model Loader. This manipulation of the argument fname causes deserialization. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. Maintainer closed #3663 same-day with no comment, PR, or fix; repo's last push (2025-11-01) predates the report, so the unsafe pickle.load in SaveLoad.load remains unguarded at develop HEAD.
A security flaw has been discovered in JusticeRage Manalyze 1.0.0. The affected element is the function PE::_parse_debug of the file manape/pe.cpp of the component PE Parser. The manipulation of the argument misc.Length results in integer underflow. The attack may be performed from remote. The patch is identified as 3e299685759f4f767088871de58c5d07f98ee382. A patch should be applied to remediate this issue.