# CVE-2026-26462: Code injection in n/a

> Remote attackers can execute arbitrary OS commands via JavaScript injection due to insecure Electron renderer configuration in the hospital management system.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2026
- **Updated:** 20 May 2026
- **Also known as:** GHSA-53vh-ccq9-xwq5

## What is CVE-2026-26462?

CVE-2026-26462 is a high-severity code injection vulnerability in n/a, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Offline Hospital Management System 5.3.0 allows remote code execution due to an improper Electron renderer configuration. The application enables Node.js integration while disabling context isolation, allowing JavaScript executed in the renderer process to access Node.js APIs and execute arbitrary operating system commands.

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement)

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


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

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

## Is CVE-2026-26462 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26462 is a high-severity code injection vulnerability in n/a, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26462 in the wild and no public exploit code.

Affected product: n/a. 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-26462/ (Markdown: https://insights.sbomify.com/CVE-2026-26462/index.md)
```

## Sources

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

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