# CVE-2026-41878: Insecure Direct Object Reference in R-SOFT DMS

> An authenticated attacker can access any file in the system by manipulating file IDs, bypassing intended access controls.

- **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:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-m5fr-qm38-x8f3

## What is CVE-2026-41878?

CVE-2026-41878 is a high-severity missing authorization vulnerability in R-SOFT SERWIS DMS, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

R-SOFT DMS is vulnerable to Insecure Direct Object Reference (IDOR) attack in multiple file download endpoints. The application fetches files from the database by ID and serves them to whoever requests them, relying only on session authentication, meaning any valid user can access any file.

This issue was fixed in version v3.19-2862 and v3.17-2580.

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

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


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

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

## Is CVE-2026-41878 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41878 is a high-severity missing authorization vulnerability in R-SOFT SERWIS DMS, published on 10 Jul 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-41878 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-41878/ (Markdown: https://insights.sbomify.com/CVE-2026-41878/index.md)
```

## Sources

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

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