{"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-44570 exists.","fix":"Upgrade open-webui to 0.6.19 or later.","what":"CVE-2026-44570 is a high-severity missing authorization vulnerability in Openwebui Open Webui, published on 15 May 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-44570 and fix it if it is affected.\n\nWhat it is: CVE-2026-44570 is a high-severity missing authorization vulnerability in Openwebui Open Webui, published on 15 May 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-44570 exists.\n\nAffected packages and fixed versions:\n- open-webui (PyPI): affected all versions; fixed in 0.6.19\n- open-webui (PyPI): affected all versions; fixed in 0.6.19\n- open-webui (PyPI): affected all versions; fixed in 0.6.19\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-44570/ (Markdown: https://insights.sbomify.com/CVE-2026-44570/index.md)","id":"CVE-2026-44570","markdown":"https://insights.sbomify.com/CVE-2026-44570/index.md","name":"CVE-2026-44570","record":{"aliases":["GHSA-hmjq-crxp-7rjw","PYSEC-2026-2733"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AI platform","requires_auth":"low_privilege","summary":"Standard users can view, delete, and restore other users' memories due to inconsistent authorization checks in the API.","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":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L","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.6.19, authorization controls surrounding the memories API were inconsistent, resulting in the ability of a standard user to delete, restore, and view the contents of other users' memories. Using a newly created non-admin user with no existing memories, it is possible to view existing memories via POST /api/v1/memories/query. Similarly, even if a non-admin user cannot modify another user's memory data via POST /api/v1/memories/{memory_id}/update, the endpoint's response improperly leaks the content of that memory if a valid memory_id is known. The DELETE /api/v1/memories/{memory_id} can also be used by any user to delete an existing memory. Deleted memories can then be restored by calling the POST /api/v1/memories/{memory_id}/update endpoint again. This vulnerability is fixed in 0.6.19.","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: Inconsistent authorization controls within memories API","id":"CVE-2026-44570","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: Improper Authorization in Standard Channels Allows Message Updates with Read Permission","id":"CVE-2026-44571"},"packages":[{"ecosystem":"PyPI","fixed":["0.6.19"],"introduced":["0"],"last_affected":[],"package":"open-webui","purl":null,"source":"GHSA-hmjq-crxp-7rjw"},{"ecosystem":"PyPI","fixed":["0.6.19"],"introduced":["0"],"last_affected":[],"package":"open-webui","purl":"pkg:pypi/open-webui","source":"GHSA-hmjq-crxp-7rjw"},{"ecosystem":"PyPI","fixed":["0.6.19"],"introduced":["0"],"last_affected":[],"package":"open-webui","purl":"pkg:pypi/open-webui","source":"PYSEC-2026-2733"}],"prev":{"headline":"Open WebUI: Insecure Message Access Breaks Authorization","id":"CVE-2026-44569"},"products":["open-webui"],"published":"2026-05-15","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":"total"},"state":"PUBLISHED","updated":"2026-05-19","vendors":["open-webui"]},"summary":"Standard users can view, delete, and restore other users' memories due to inconsistent authorization checks in the API.","url":"https://insights.sbomify.com/CVE-2026-44570/"}