# CVE-2026-41879: Weak password hashing in R-SOFT DMS

> Weak non-salted MD5 hashing of superadmin credentials allows attackers to decode passwords and gain administrative access.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-2mx5-42xw-7586

## What is CVE-2026-41879?

CVE-2026-41879 is a high-severity vulnerability in R-SOFT SERWIS DMS, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

R-SOFT DMS stores superadmin credentials using a non-salted nested MD5 hash. This allows an attacker who obtain password hash to decode superadmin credentials. Critically, this password cannot be changed except by modifying the configuration file.

This issue was fixed in version v3.17-2000.

Weakness: CWE-328 (Use of Weak Hash)

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


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

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

## Is CVE-2026-41879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41879 is a high-severity vulnerability in R-SOFT SERWIS DMS, published on 10 Jul 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-41879 in the wild and no public exploit code.

Affected product: R-SOFT SERWIS DMS. 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-41879/ (Markdown: https://insights.sbomify.com/CVE-2026-41879/index.md)
```

## Sources

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

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