Two significant industry-wide security issues were disclosed in mid-October 2026: critical vulnerabilities affecting PHP, commonly referred to as PHP2Shell, and a separate incident involving compromised eMudhra (emSign) intermediate certificates.
SBI Coinhako is not affected by the recently disclosed PHP2Shell vulnerabilities or the eMudhra certificate incident, and your assets remain protected. Our assessment confirmed that our platform does not run affected PHP versions and does not rely on certificates issued by the affected eMudhra intermediates.
Our Security team assessed both issues as soon as they were disclosed. Our core trading, wallet and custody systems do not run on the affected PHP components, and we do not rely on the affected eMudhra certificates.
We continue to monitor developments closely and strengthen our security controls to help keep our platform and users protected.
What is PHP2Shell?
On 21 October 2026, the PHP development team released security updates addressing two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619.
The vulnerabilities allow unauthenticated remote code execution on affected systems, which means that an attacker could potentially run code on a vulnerable web server without logging in. PHP has advised users of affected versions to immediately update to the fixed releases, noting that updating is the only complete protection against the vulnerabilities.
Cybersecurity authorities, including JPCERT/CC in Japan, have also issued alerts recommending that organisations using affected PHP versions apply the security updates promptly and investigate systems for signs of compromise.
What is the eMudhra certificate incident?
On 20 October 2026, Mozilla and Google’s Chrome Root Program publicly confirmed that the private keys of eight intermediate Certificate Authority (CA) certificates operated by eMudhra had been compromised. eMudhra is an India-based certificate authority that issues certificates under the emSign brand. The issue was first reported by a security researcher on 17 October 2026 and was traced to a flaw in how the keys were generated. Six of the affected certificates were used to issue website (TLS) certificates and two were used for code signing.
Compromised certificate keys could potentially be used to create fraudulent certificates that impersonate legitimate websites under certain circumstances.
eMudhra has stated that the incident is limited to the affected intermediate certificates and does not involve its root CA private keys. Major browser and certificate ecosystem providers have also taken steps to block or distrust the affected certificates.
Keeping your assets protected
As SBI Coinhako is not affected by these security incidents, no further action is required from our users. However, as good practice, we recommend keeping your browser, operating system and SBI Coinhako app up to date, as recent updates include protections against the affected certificates.
Your assets remain protected, and our Security team continuously reviews and strengthens our security controls to help safeguard our platform and users.
As always, we encourage users to stay vigilant against phishing attempts and only access SBI Coinhako through our official website and applications. SBI Coinhako will never ask for your password, 2FA codes or recovery phrases.
Our Help Centre has practical guides to help you keep your account secure, explore all our security resources in the Account Management & Security section.
If you have any questions relating to your SBI Coinhako account or assets, please contact us at hello@coinhako.com or submit a ticket via here. We're always happy to help.