Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-94382 medium CVSS 4.2

Vulnerability in Beszel (CVE-2026-94382)

Summary

Vulnerability in Beszel (CVE-2026-94382). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /api/beszel/user-alerts.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-94382 has been found in Beszel.
Attackers can target a specific entry point like DELETE /api/beszel/user-alerts over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Beszel CVE-2026-94382" on the vendor's site.

CVE-2026-94382 (Beszel) — CWE-639 / CVSS v3 4.2
Attack vector: remote (network-reachable) / no user interaction
Attack surface: DELETE /api/beszel/user-alerts
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in Beszel. Attackers reach the vulnerable code path via DELETE /api/beszel/user-alerts.

📍 Affected scope

Check the vendor advisory for the affected versions of Beszel. Attack surface: DELETE /api/beszel/user-alerts.

🔥 Severity

Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /api/beszel/user-alerts requests with malformed payloads or SQL meta-characters. Run grep -r 'Beszel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Beszel' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Beszel を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'DELETE /api/beszel/user-alerts' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで DELETE /api/beszel/user-alerts への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against DELETE /api/beszel/user-alerts on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details