{"answers":{"affected":"3 open source packages ship an affected version, including open-webui. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54006 exists.","fix":"Upgrade open-webui to 0.9.6 or later.","what":"CVE-2026-54006 is a medium-severity missing authorization vulnerability in Openwebui Open Webui, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54006 and fix it if it is affected.\n\nWhat it is: CVE-2026-54006 is a medium-severity missing authorization vulnerability in Openwebui Open Webui, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54006 exists.\n\nAffected packages and fixed versions:\n- open-webui (PyPI): affected all versions; fixed in 0.9.6\n- open-webui (PyPI): affected all versions; fixed in 0.9.6\n- open-webui (PyPI): affected all versions; fixed in 0.9.6\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54006/ (Markdown: https://insights.sbomify.com/CVE-2026-54006/index.md)","id":"CVE-2026-54006","markdown":"https://insights.sbomify.com/CVE-2026-54006/index.md","name":"CVE-2026-54006","record":{"aliases":["GHSA-f3g7-59qc-pqg6","PYSEC-2026-2722"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI platform","requires_auth":"low_privilege","summary":"Attackers can move calendar events into other users' calendars by bypassing destination authorization checks, allowing unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"open_webui","vendor":"openwebui"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.6, POST /api/v1/calendars/events/{event_id}/update validates that the caller has write access to the calendar the event currently belongs to, but does not validate the destination calendar_id supplied in the request body. The model layer then persists the new calendar_id unconditionally. A regular user-role account can therefore create an event in their own calendar and immediately move it into any other user's calendar whose ID they know — bypassing the authorization check that create_event correctly performs.  This vulnerability is fixed in 0.9.6.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Open WebUI: Calendar event re-parenting allows writing events into another user's calendar","id":"CVE-2026-54006","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"openwebui:open_webui","products":["openwebui:open_webui"],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Open WebUI: Cross-origin postMessage confirmation bypass via action:submit","id":"CVE-2026-54007"},"packages":[{"ecosystem":"PyPI","fixed":["0.9.6"],"introduced":["0"],"last_affected":[],"package":"open-webui","purl":null,"source":"GHSA-f3g7-59qc-pqg6"},{"ecosystem":"PyPI","fixed":["0.9.6"],"introduced":["0"],"last_affected":[],"package":"open-webui","purl":"pkg:pypi/open-webui","source":"GHSA-f3g7-59qc-pqg6"},{"ecosystem":"PyPI","fixed":["0.9.6"],"introduced":["0"],"last_affected":[],"package":"open-webui","purl":"pkg:pypi/open-webui","source":"PYSEC-2026-2722"}],"prev":{"headline":"Kirby: `pages.access` permission is not checked in the `site/find` REST API route","id":"CVE-2026-54005"},"products":["open-webui"],"published":"2026-06-23","related":[{"cvss_score":9.1,"headline":"Open WebUI: LDAP Empty Password Authentication Bypass","id":"CVE-2026-44551","kev_date_added":null,"published":"2026-05-15"},{"cvss_score":9,"headline":"open-webui - Remote Code Execution via CORS Misconfiguration and Session Validation","id":"CVE-2026-56400","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":9,"headline":"Cross-site Scripting (XSS) in open-webui/open-webui","id":"CVE-2024-8017","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.8,"headline":"Open WebUI: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed","id":"CVE-2026-45672","kev_date_added":null,"published":"2026-05-15"},{"cvss_score":8.7,"headline":"Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin","id":"CVE-2026-87995","kev_date_added":null,"published":"2026-09-09"},{"cvss_score":8.7,"headline":"Open WebUI: Stored XSS via unescaped KaTeX render-error fallback in rendered messages","id":"CVE-2026-70492","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":8.7,"headline":"Open WebUI: Stored XSS in Mermaid Markdown Preview","id":"CVE-2026-54011","kev_date_added":null,"published":"2026-06-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["open-webui"]},"summary":"Attackers can move calendar events into other users' calendars by bypassing destination authorization checks, allowing unauthorized data modification.","url":"https://insights.sbomify.com/CVE-2026-54006/"}