# CVE-2026-42517: Cryptographic Failure Vulnerability in e-Sushrut HMIS

> An authenticated attacker can decode Base64 parameters to access sensitive data and gain unauthorized access in the e-Sushrut HMIS.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-gq82-hp87-wfrg

## What is CVE-2026-42517?

CVE-2026-42517 is a high-severity vulnerability in CDAC-Noida e-Sushrut, Hospital Management Information System (HMIS), published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This vulnerability exists in e-Sushrut due to the use of reversible Base64 encoding for protecting sensitive data. An authenticated attacker could exploit this vulnerability by decoding and manipulating Base64-encoded parameters in the request URL to gain unauthorized access to sensitive information on the targeted system.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-42517?


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

No fix has been published for CVE-2026-42517 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42517 being exploited?

There is no known exploitation of CVE-2026-42517 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42517 and fix it if it is affected.

What it is: CVE-2026-42517 is a high-severity vulnerability in CDAC-Noida e-Sushrut, Hospital Management Information System (HMIS), published on 29 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42517 in the wild and no public exploit code.

Affected product: CDAC-Noida e-Sushrut, Hospital Management Information System (HMIS). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42517/ (Markdown: https://insights.sbomify.com/CVE-2026-42517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42517
- OSV: https://osv.dev/vulnerability/CVE-2026-42517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42517/
Summaries are generated and may contain mistakes; the official description above is the record.