# CVE-2026-130873: ep3-bs through 1.9.1b Improper Authorization via UserController deleteAction


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-rp3r-3gcx-797j

## What is CVE-2026-130873?

CVE-2026-130873 is a medium-severity vulnerability in tkrebs ep3-bs, published on 17 Nov 2026. 

### Official description

ep3-bs through 1.9.1b contains an improper authorization vulnerability that allows staff users with only user management privilege to delete administrator accounts. Authenticated assistant accounts can invoke the backend UserController deleteAction against administrator targets to remove or mark them deleted, locking administrators out.

Weakness: CWE-863 (Incorrect Authorization)

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

1 open source package ship an affected version, including tkrebs/ep3-bs.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `tkrebs/ep3-bs` | GitHub | `pkg:github/tkrebs/ep3-bs` | All versions to 1.9.1b | None |

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

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

## Is CVE-2026-130873 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130873 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130873 is a medium-severity vulnerability in tkrebs ep3-bs, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130873 exists.

Affected packages and fixed versions:
- tkrebs/ep3-bs (GitHub): affected all versions up to 1.9.1b; no fix listed

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-130873/ (Markdown: https://insights.sbomify.com/CVE-2026-130873/index.md)
```

## Sources

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

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