# CVE-2026-109119: Missing Authorization in rdiffweb

> Authenticated users can elevate privileges to administrator by modifying the role parameter in the user management API.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-cq7f-c253-x96p

## What is CVE-2026-109119?

CVE-2026-109119 is a high-severity missing authorization vulnerability in ikus-soft rdiffweb, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Privilege Management in the user management API endpoint (/api/users/{username_or_id}) in Rdiffweb allows authenticated users to elevate their privileges to administrator by modifying the role parameter in a POST request.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109119 is a high-severity missing authorization vulnerability in ikus-soft rdiffweb, published on 16 Oct 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-109119 in the wild and no public exploit code.

Affected product: ikus-soft rdiffweb. 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-109119/ (Markdown: https://insights.sbomify.com/CVE-2026-109119/index.md)
```

## Sources

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

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