CERT-In’s vulnerability note, CIVN-2026-0557, issued on November 17, 2026, rates several flaws in C-DAC’s e-Sushrut HMIS as high severity. An unauthenticated remote attacker could access hospital dashboard information, internal operational statistics, and sensitive patient data, or launch authentication-related attacks against a healthcare organisation. The advisory recommends contacting C-DAC and upgrading to the latest version.
What CERT-In found
CERT-In identified four distinct vulnerabilities, each assigned a Common Vulnerabilities and Exposures (CVE) identifier.
1. Improper authentication (CVE-2026-124643)
The first vulnerability arises from insufficient authentication and session validation in the software’s dashboard functionality.
According to CERT-In, an unauthenticated attacker could send specially crafted HTTP requests to a vulnerable endpoint and gain unauthorised access to hospital dashboard information. This indicates that the software may not properly verify user permissions before allowing dashboard access.
2. Sensitive information disclosure (CVE-2026-124644)
The second vulnerability exposes internal hospital operational statistics through data embedded in the HTML response of the software’s login page.
CERT-In stated that an unauthenticated attacker could access the login page, examine its HTML content, and extract internal hospital operational information. This vulnerability allows information to be exposed without requiring a login or valid credentials.
3. Hardcoded cryptographic key (CVE-2026-124645)
The third vulnerability concerns the software’s client-side password hashing mechanism, which uses a static and predictable value embedded in the login page.
Password hashing converts a password into a different value during authentication. CERT-In found that attackers could extract the embedded value and replicate the hashing process. The agency warned that this could weaken the authentication mechanism and increase the risk of attacks against healthcare organisations using e-Sushrut.
4. Insecure Direct Object Reference (CVE-2026-124646)
The fourth vulnerability involves insufficient server-side authorisation checks in an API endpoint. An Insecure Direct Object Reference (IDOR) occurs when a system fails to properly verify whether a user is authorised to access specific resources or records.
CERT-In stated that an unauthenticated attacker could exploit this weakness by modifying a parameter in an API request. This could allow the attacker to enumerate records and gain unauthorised access to sensitive patient information held by a healthcare organisation. Unlike the vulnerabilities affecting dashboard information and operational statistics, this flaw directly increases the risk of exposing individual patient records.
CERT-In advises hospitals to upgrade e-Sushrut
CERT-In has advised organisations using e-Sushrut to contact C-DAC and upgrade to the latest software version to address the identified vulnerabilities. The advisory names C-DAC Noida as the vendor and identifies e-Sushrut users, administrators, and patients as the affected groups.
CERT-In credited two security researchers with identifying the vulnerabilities. Rylen Anil reported the issues related to improper authentication, sensitive information disclosure, and hardcoded cryptographic keys. Sriharan Mahendran reported the IDOR vulnerability.
Not the first warning for this product
CERT-In had previously flagged vulnerabilities in e-Sushrut. In its April 28, 2026 note, CIVN-2026-0207, the agency rated the product’s flaws as critical. It identified authentication bypass and unauthorised access to user accounts or data across five CVEs (CVE-2026-42513 to CVE-2026-42517):
- A login check that trusted client-side response parameters, allowing a remote attacker to tamper with the server response and bypass authentication. This vulnerability received a score of 8.8.
- One vulnerability exposed one-time passwords (OTPs) in plaintext in API responses.
- An insecure direct object reference allowed an authenticated user to alter an API URL parameter and view other patients’ sensitive information.
- A second broken access control flaw allowed an authenticated user to view or modify patient accounts by manipulating encoded parameters.
- One vulnerability left sensitive data protected only by reversible Base64 encoding.
The April advisory recommended an upgrade, as the vendor had not provided a workaround. Although the November vulnerabilities affect different components, CERT-In has again flagged the same product for weaknesses involving authentication and data exposure.
What remains unanswered
- Whether C-DAC has issued a public statement on the vulnerabilities.
- Which software version fixes the identified flaws.
- Further technical details about the four November CVEs.
- Whether any hospital has suffered a breach involving these vulnerabilities.
Also read:

