Comparison Overview
Standard Chartered India

Standard Chartered India
N/A
Last Update: 05/02/2026
Standard Chartered Bank has been operating in India for over 160 years, making it one of the oldest foreign banks. The Bank has a network of 100 branches across 42 cities. Key business segments include Corporate, Commercial and Institutional Banking and Consumer, Privat...

Banco de Crédito BCP
Calle Centenario 156, La Molina, Lima 12, PE
Last Update: 02/04/2026
Somos el banco peruano que desde hace más de 130 años viene liderando el sistema financiero a nivel nacional. A lo largo de todo este tiempo hemos contribuido con el desarrollo económico de nuestro país, transformando planes en realidad. Todo esto es posible gracias a...
Compliance Ranges Comparison

Standard Chartered India







Banco de Crédito BCP






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Standard Chartered India in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco de Crédito BCP in 2026.
Incident History - Standard Chartered India (X = Date, Y = Severity)
Standard Chartered India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco de Crédito BCP (X = Date, Y = Severity)
Banco de Crédito BCP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Standard Chartered India

Banco de Crédito BCP
FAQ
Latest Global CVEs
A security vulnerability has been detected in Sipeed PicoClaw up to 0.2.9. The affected element is the function handleMessageReceive of the file pkg/channels/feishu/feishu_64.go of the component Group Message Handler. Such manipulation leads to missing authorization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The reported GitHub issue was closed automatically due to inactivity.
A weakness has been identified in Sipeed PicoClaw up to 0.2.9. Impacted is the function isPrivateOrRestrictedIP of the file pkg/tools/integration/web.go of the component web_fetch. This manipulation causes server-side request forgery. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. Patch name: 2efbe5d560e7ed9bc5209c203dc4aa6ecdbc7405. To fix this issue, it is recommended to deploy a patch.
- https://github.com/sipeed/picoclaw/
- https://github.com/sipeed/picoclaw/commit/2efbe5d560e7ed9bc5209c203dc4aa6ecdbc7405
- https://github.com/sipeed/picoclaw/issues/3077
- https://github.com/sipeed/picoclaw/pull/3085
- https://vuldb.com/cve/CVE-2026-16196
- https://vuldb.com/submit/852963
- https://vuldb.com/vuln/380012
- https://vuldb.com/vuln/380012/cti
A security flaw has been discovered in Sipeed PicoClaw up to 0.2.9. This issue affects the function dispatchIncoming of the file pkg/channels/wecom/wecom.go of the component Group Message Handler. The manipulation results in incorrect authorization. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The reported GitHub issue was closed automatically due to inactivity.
QueryWeaver contains an authentication bypass vulnerability that allows unauthenticated attackers to obtain valid session tokens for existing accounts by submitting a signup request with a known victim email address. The signup route unconditionally creates and links a new token to the matching Identity via a Cypher MERGE operation before checking whether the email belongs to an existing account, causing the server to return a valid authenticated session token for the victim's identity without requiring any prior credentials or user interaction.
A vulnerability was determined in zhayujie CowAgent up to 2.1.1. This affects the function WebFetch.execute of the file agent/tools/web_fetch/web_fetch.py. Executing a manipulation of the argument url can lead to server-side request forgery. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.1.2 is able to mitigate this issue. This patch is called ea47f3097eed4f8295c4cb3d76ecb97e0f43d632. It is recommended to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
- https://github.com/zhayujie/CowAgent/
- https://github.com/zhayujie/CowAgent/commit/ea47f3097eed4f8295c4cb3d76ecb97e0f43d632
- https://github.com/zhayujie/CowAgent/issues/2889
- https://github.com/zhayujie/CowAgent/pull/2900
- https://github.com/zhayujie/CowAgent/releases/tag/2.1.2
- https://vuldb.com/cve/CVE-2026-16194
- https://vuldb.com/submit/857620
- https://vuldb.com/vuln/380009
- https://vuldb.com/vuln/380009/cti