MISFIRE

Browse / Unbounded Consumption / CVE-2026-45667

Open WebUI: Unauthenticated endpoint can trigger embedding generation (cost/DoS)

CVE-2026-45667 ยท 2026-05-14 moderate

Class
Unbounded Consumption (filed by a model that read the source)
Technique
Authentication and access control
Also involves
AI Framework and Platform Flaws
Affected
open-webui (PyPI)
Gets past
Authentication check
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS
0.3% chance of exploitation in 30 days

How it works, in short

An endpoint that runs the embedding function needs no login, so anonymous callers can trigger repeated embedding computation and paid provider calls. (Our summary, written by a model. The source text is below.)

Details

Summary

GET /api/v1/memories/ef is accessible without authentication and executes request.app.state.EMBEDDING_FUNCTION(...). This allows any unauthenticated caller to trigger embedding generation which can lead to direct cost exposure if a paid provider is used. Code reference: backend/open_webui/routers/memories.py (@router.get("/ef") -> calls request.app.state.EMBEDDING_FUNCTION("hello world")).

Details

GET /api/v1/memories/ef is reachable without authentication and triggers request.app.state.EMBEDDING_FUNCTION("hello world"). This crosses an intended security boundary by allowing unauthenticated users to invoke potentially expensive embedding computation and/or paid upstream embedding APIs.

PoC

1. Start Open WebUI in default configuration (no special env hardening; default ENABLE_MEMORIES is true). 2. From an unauthenticated client (no cookies/Authorization header), call: curl -i http://\<host\>:\<port\>/api/v1/memories/ef 3. Observe the server performs embedding generation and returns a response like: - HTTP 200 with JSON containing the result.

How it can be abused / attacker actions:

Resolution

Fixed in commit e5035ea31, first released in v0.8.0 (Feb 2026). The /api/v1/memories/ef route was removed entirely. It was a diagnostic/debug-style endpoint that hard-coded "hello world" through the embedding function without any authentication dependency; there was no legitimate caller that depended on it, so deletion was the cleaner fix than retrofitting auth. Users on >= 0.8.0 are not affected.

References

Source: GitHub Advisory Database, used under CC BY 4.0.