# CVE-2026-94382: Beszel before 0.19.0 Insecure Direct Object Reference via user-alerts

> Authenticated users can create or delete alerts on unauthorized systems, leading to information disclosure and data modification.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/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:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-759g-ch5m-2gch, GHSA-x7pw-mf2h-rgr4

## What is CVE-2026-94382?

CVE-2026-94382 is a low-severity missing authorization vulnerability in henrygd beszel, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Beszel before 0.19.0 contains an insecure direct object reference vulnerability in the POST and DELETE /api/beszel/user-alerts handlers that allows any authenticated user to create or delete alerts on systems they cannot access. Attackers can supply arbitrary system IDs in the request body to register alert rules and receive notifications disclosing target system names and metrics.

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

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


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

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

## Is CVE-2026-94382 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94382 is a low-severity missing authorization vulnerability in henrygd beszel, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-94382 exists.

Affected product: henrygd beszel. 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-94382/ (Markdown: https://insights.sbomify.com/CVE-2026-94382/index.md)
```

## Sources

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

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