Incident sheet · /security

Filed
Read
3 min · 590 words
Severity
Routine

CERT-In flags 4 high-severity e-Sushrut flaws, warns of data exposure

CERT-In’s November 17 advisory flags four high-severity e-Sushrut flaws, including unauthenticated patient-data access, after five critical CVEs in April.

CERT-In flags 4 high-severity flaws in C-DAC’s e-Sushrut hospital software, warns of patient data exposure risks
FeedCERT-In flags 4 high-severity flaws in C-DAC’s e-Sushrut hospital software, warns of patient data exposure risks — Bru-nO / pixabay

Event log

  1. CERT-In issued CIVN-2026-0557 on November 17, 2026, flagging four high-severity e-Sushrut vulnerabilities.
  2. Three November findings explicitly describe access without valid credentials, including patient-record enumeration.
  3. CERT-In advised organisations using e-Sushrut to contact C-DAC and upgrade to the latest version.
  4. An April 28, 2026 note rated five flaws critical under CVE-2026-42513 through CVE-2026-42517.
  5. The fixed e-Sushrut version and any hospital breach remain unknown.

By Olivia Hart

On November 17, 2026, CERT-In detailed a hospital cyberattack path: four high-severity flaws in C-DAC Noida’s e-Sushrut hospital management information system could expose dashboards, internal statistics and sensitive patient records to an unauthenticated remote attacker.

The vulnerability note, CIVN-2026-0557, also warned of authentication-related attacks against healthcare organisations using e-Sushrut. CERT-In named users, administrators and patients as affected groups and instructed organisations to contact C-DAC and upgrade to the latest version.

The four vulnerabilities

  • Improper authentication and session validation (CVE-2026-124643): Insufficient checks in the dashboard let an unauthenticated attacker send crafted HTTP requests to a vulnerable endpoint and gain unauthorised access. CERT-In said “the software may not properly verify user permissions before allowing dashboard access.”

  • Sensitive information disclosure (CVE-2026-124644): The login page’s HTML response embedded internal hospital operational statistics. An unauthenticated attacker could open that page, inspect its HTML and extract the data without a login or valid credentials.

  • Hardcoded cryptographic key (CVE-2026-124645): The client-side password-hashing mechanism used a static, predictable value embedded in the login page. Attackers could extract it and replicate the hashing process. CERT-In warned this “could weaken the authentication mechanism and increase the risk of attacks against healthcare organisations using e-Sushrut.”

  • Insecure Direct Object Reference (CVE-2026-124646): Insufficient server-side authorisation checks on an API endpoint could let an unauthenticated attacker modify a request parameter, enumerate records and access sensitive patient information. Unlike the dashboard and operational-statistics flaws, this weakness created a direct route to individual patient records.

  • CERT-In credited Rylen Anil with the improper-authentication, sensitive-information-disclosure and hardcoded-key findings. It credited Sriharan Mahendran with the IDOR finding.

    What does this change for hospitals using e-Sushrut?

    CERT-In’s practical instruction is straightforward: contact C-DAC and upgrade to the latest version. The note also shows that signing in is not a prerequisite for several attack paths. Crafted dashboard requests, login-page HTML inspection and API-parameter tampering all describe access without valid credentials.

    For hospital operators, the upgrade is therefore the immediate action to pursue. The advisory did not identify which software version contains the fixes, leaving deployment teams without a named target release.

    A critical warning in April

    On April 28, 2026, CERT-In issued CIVN-2026-0207 and rated e-Sushrut’s flaws critical across five CVEs, CVE-2026-42513 through CVE-2026-42517:

    • A login check trusted client-side response parameters, allowing a remote attacker to tamper with the server response and bypass authentication. CERT-In scored it 8.8.
    • One flaw exposed one-time passwords in plaintext in API responses.
    • An IDOR let an authenticated user alter an API URL parameter and view other patients’ sensitive information.
    • A second broken-access-control flaw let an authenticated user view or modify patient accounts by manipulating encoded parameters.
    • Another flaw protected sensitive data only with reversible Base64 encoding.

    The April advisory recommended an upgrade because the vendor had not provided a workaround. Although the November vulnerabilities affect different components, CERT-In again found authentication weaknesses and routes to data exposure.

    Unanswered questions

    • Whether C-DAC has issued a public statement about the four November 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.

    For hospitals, the remediation direction is clear; the fixed build, public vendor response and evidence of any hospital breach are not.

    via medianama.com (Source)

    Filed under

    • e-sushrut
    • cert
    • healthcare-security
    • patient-data
    • vulnerability-management
    Share this article:

    More from Olivia Hart

    Olivia Hart

    Show full bio

    News editor covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

    207 articles

    The newsroom digest

    One email a day with the stories that matter. No noise.

    By subscribing you agree to the privacy policy.

    Cross-references

    ‹ Previous articleNext article ›