Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-87012 medium CVSS 4.3

Vulnerability in open-webui (CVE-2026-87012)

Summary

Vulnerability in open-webui (CVE-2026-87012). Risk of unauthorized operations or information disclosure. Exploitable via meta. Mitigation: upgrade to 0.11.1 or later.

Original description

The description as published by the source.

Any authenticated user can suppress calendar alerts instance-wide via a non-numeric alert value

Summary

Calendar events carry a free-form meta object that is stored exactly as submitted, with no validation of the values inside it. The scheduler reads the per-event alert offset out of that object in a single pass that covers every user's upcoming events, and compares it numerically without checking that it is a number. Any verified user could store a text value there, which made the comparison raise and abort the whole pass, so no calendar reminder fired for anyone on the instance while that event stayed inside the lookahead window.

Preconditions

  • Calendar is enabled (ENABLE_CALENDAR / calendar.enable, default True).
  • The attacker is a verified user (role user or admin) holding the calendar feature permission, which is granted to all users by default (USER_PERMISSIONS_FEATURES_CALENDAR, default True).
  • The event's start time falls inside the scheduler's one hour lookahead window, so the shared alert pass selects it.

No admin access, no shared calendar, no recurrence rule and no open registration are required, an invited account is enough. Deployments running with the calendar disabled, or with the calendar feature permission removed from regular users, are not affected.

Impact

Availability loss on one feature, affecting every user on the instance. While a single event carrying a non-numeric alert value sat in the upcoming window, the shar…

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-87012 has been found in open-webui.
Attackers can target a specific entry point like meta over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade open-webui to 0.11.1 or later.
If unsure, ask your IT team or search "open-webui CVE-2026-87012" on the vendor's site.

CVE-2026-87012 (open-webui) — CWE-754 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: meta / ENABLE_CALENDAR / calendar.enable / True
Patched: 0.11.1 — apply immediately
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-754) exists in open-webui. Attackers reach the vulnerable code path via meta.

📍 Affected scope

Check the vendor advisory for the affected versions of open-webui. Attack surface: meta / ENABLE_CALENDAR / calendar.enable / True.

🔥 Severity

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

🔧 How to fix

Update to 0.11.1.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'open-webui' . 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 'open-webui' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade open-webui to 0.11.1

    ステージング環境で 0.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

pip open-webui
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.11.1"}]}]

References

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