# Open WebUI's API key endpoint restrictions bypassed via \`x-api-key\` header — full message processing on restricted endpoints

Advisory record · `GHSA-57q6-fvp4-pqmm`

- **Identifiers:** `GHSA-57q6-fvp4-pqmm` · `CVE-2026-45339` · `PYSEC-2026-3543`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 14 May 2026
- **Updated:** 3 Nov 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2026, 20:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `open-webui` (PyPI): affected `<0.9.0`; fixed in `0.9.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Open WebUI versions before 0.9.0 are affected. An API key that has been restricted from certain endpoints can bypass those restrictions by sending the key in the x-api-key header instead of Authorization, which lets it reach the restricted endpoint, invoke a model, and receive a full response. Upgrade to Open WebUI 0.9.0 or later. No workaround is given.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0031, the 24th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 May 2026, 20:21 UTC: [Confirmed by GitHub Advisory Database](https://github.com/advisories/GHSA-57q6-fvp4-pqmm)
- 15 May 2026, 20:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-45339)
- 31 Oct 2026, 14:41 UTC: First seen by agentprime
- 31 Oct 2026, 14:41 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-57q6-fvp4-pqmm)

## Sources

- [GitHub Advisory Database: GHSA-57q6-fvp4-pqmm](https://github.com/advisories/GHSA-57q6-fvp4-pqmm)
- [OSV: GHSA-57q6-fvp4-pqmm](https://osv.dev/vulnerability/GHSA-57q6-fvp4-pqmm)
- <https://github.com/open-webui/open-webui/security/advisories/GHSA-57q6-fvp4-pqmm>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-45339>
- <https://github.com/advisories/GHSA-57q6-fvp4-pqmm>
- <https://github.com/open-webui/open-webui>
- <https://github.com/open-webui/open-webui/releases/tag/v0.9.0>
- <https://github.com/pypa/advisory-database/tree/main/vulns/open-webui/PYSEC-2026-3543.yaml>
- <https://pypi.org/project/open-webui>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-57q6-fvp4-pqmm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-57q6-fvp4-pqmm/>. Everything for agents: <https://agentprime.io/llms.txt>.
