VulnerabilityPublished 23 Sep 2025Updated 28 Oct 2025

CVE-2025-56146: Indian Bank IndSMART Android App · Missing Validation of OpenSSL Certificate

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability, Indian Bank should urgently update the IndSMART app to enforce strict SSL certificate validation within the NuWebViewActivity component, ensuring that all SSL/TLS connections verify certificates against trusted certificate authorities and reject invalid or self-signed certificates. Organizations and users should avoid using the app on untrusted or public networks until a patch is available. Employing VPNs can add an additional layer of encryption to protect data in transit. Network monitoring tools should be configured to detect unusual SSL/TLS traffic patterns indicative of MitM attempts. Security teams should educate users about the risks of connecting to unsecured Wi-Fi and encourage the use of mobile data or trusted networks when accessing banking apps. Additionally, implementing certificate pinning in the app can further reduce the risk of MitM attacks by binding the app to specific certificates or public keys. Finally, organizations should maintain up-to-date mobile device management (MDM) policies to enforce app updates and security configurations.

Description

Indian Bank IndSMART Android App 3.8.1 is vulnerable to Missing SSL Certificate Validation in NuWebViewActivity.

Impact

For European organizations, the primary impact of this vulnerability is the potential compromise of confidentiality of sensitive banking data transmitted via the Indian Bank IndSMART app. Although the app is targeted at Indian Bank customers, European entities with employees or customers using this app, or those engaged in financial transactions with Indian Bank, could be indirectly affected. The exposure could lead to leakage of personal identifiable information (PII), banking credentials, or transaction details if an attacker successfully executes a MitM attack on unsecured networks such as public Wi-Fi. This could facilitate fraud, identity theft, or unauthorized access to banking services. However, since the vulnerability does not affect integrity or availability, the risk of data tampering or service disruption is low. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often weaponize such vulnerabilities once disclosed. The medium severity rating suggests that while the threat is not critical, it warrants timely remediation to protect user data and maintain trust in banking applications.

CWE-599Missing Validation of OpenSSL Certificate (opens in a new tab)
Variant weakness
The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.
Architecture and Design
Ensure that proper authentication is included in the system design.
Implementation
Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

medium.com/@parvbajaj2000/cve-2025-56146-missing-ssl-certificate-validation-in-indian-bank-indsmart-android-app-9db200ac1c69 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Oct 2025, 20:45 UTC

WeaknessesCWE-599

Technical details

References

Community reviews

Related threats