# CVE-2026-42251: Hard-coded credentials in KS-SOMED

> Hard-coded credentials allowed attackers to upload malicious updates to the FTP server, potentially leading to code execution on client machines.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-vqmx-wc76-rxc7

## What is CVE-2026-42251?

CVE-2026-42251 is a high-severity vulnerability in KAMSOFT KS-SOMED, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded credentials in KS-SOMED allowed an unauthorized attacker access to FTP server that hosted the application's update packages. The attacker with these credentials could upload a malicious update file, which then may have been distributed and installed on client machines as a legitimate update.

This issue affects KS-SOMED with modules: KSPLUPDFTP.exe up to 30.00.00.056 and ANEKSKLIENT.EXE up to 29.00.02.026

Beside removing the hard-coded credentials from the code and changing the update process, access granted by previously exposed credentials was limited to read-only.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-42251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42251 is a high-severity vulnerability in KAMSOFT KS-SOMED, published on 1 Jun 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-42251 in the wild and no public exploit code.

Affected product: KAMSOFT KS-SOMED. 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-42251/ (Markdown: https://insights.sbomify.com/CVE-2026-42251/index.md)
```

## Sources

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

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