{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43889 exists.","fix":"No fix has been published for CVE-2026-43889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-43889 is a medium-severity missing authorization vulnerability in outline, published on 11 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-43889 and fix it if it is affected.\n\nWhat it is: CVE-2026-43889 is a medium-severity missing authorization vulnerability in outline, published on 11 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-43889 exists.\n\nAffected product: outline. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-43889/ (Markdown: https://insights.sbomify.com/CVE-2026-43889/index.md)","id":"CVE-2026-43889","markdown":"https://insights.sbomify.com/CVE-2026-43889/index.md","name":"CVE-2026-43889","record":{"aliases":["GHSA-rg4j-pmch-w6pm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Collaborative documentation service","requires_auth":"low_privilege","summary":"Attackers can publish unauthorized documents by exploiting flawed permission checks in the sharing API, exposing private content to unauthenticated users.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Outline is a service that allows for collaborative documentation. Prior to 1.7.0, the shares.create API accepts both collectionId and documentId simultaneously and, when published=false, only verifies read access for each—skipping the \"share\" permission check. A subsequent shares.update authorizes publication using an OR policy (can share collection OR can share document), so an attacker who holds share permission on one unrelated collection can publish a share that exposes an arbitrary document they cannot legitimately share, making it publicly accessible to unauthenticated users. This vulnerability is fixed in 1.7.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Outline: Unauthorized Document Publication via Mixed collectionId+documentId Share","id":"CVE-2026-43889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in outline","id":"CVE-2026-43890"},"packages":[],"prev":{"headline":"Outline: Zip Extraction Path Escape via PATH_MAX Truncation in Collection Import","id":"CVE-2026-43888"},"products":["outline"],"published":"2026-05-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-12","vendors":["outline"]},"summary":"Attackers can publish unauthorized documents by exploiting flawed permission checks in the sharing API, exposing private content to unauthenticated users.","url":"https://insights.sbomify.com/CVE-2026-43889/"}