{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44695 exists.","fix":"No fix has been published for CVE-2026-44695 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44695 is a medium-severity vulnerability in outline, published on 11 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44695 and fix it if it is affected.\n\nWhat it is: CVE-2026-44695 is a medium-severity vulnerability in outline, published on 11 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44695 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-44695/ (Markdown: https://insights.sbomify.com/CVE-2026-44695/index.md)","id":"CVE-2026-44695","markdown":"https://insights.sbomify.com/CVE-2026-44695/index.md","name":"CVE-2026-44695","record":{"aliases":["GHSA-mjgw-5j7q-gv8v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Outline documentation service","requires_auth":"low_privilege","summary":"Attackers can link victim Outline accounts to attacker Slack identities via unsigned OAuth state, enabling unauthorized access to victim data.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"outline","vendor":"getoutline"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Outline is a service that allows for collaborative documentation. Prior to 1.7.1, the Slack integration callback for GET /auth/slack.post accepts an unsigned, session-independent OAuth state value. A third party who can obtain a Slack OAuth code for the same Outline Slack client can make a logged-in Outline user complete the callback and link that user's Outline account to the attacker's Slack team_id and user_id. The linked Slack identity can then use the Slack /outline search command as the victim Outline user. This vulnerability is fixed in 1.7.1.","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: Slack OAuth state can link a victim Outline account to an attacker Slack identity","id":"CVE-2026-44695","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenProject: Stored CSS injection via Sanitize::Config::RELAXED[:css] enables phishing overlays and data exfiltration","id":"CVE-2026-44696"},"packages":[],"prev":{"headline":"n8n-MCP: Authenticated SSRF in n8n-mcp webhook and API client paths","id":"CVE-2026-44694"},"products":["outline"],"published":"2026-05-11","related":[{"cvss_score":9.1,"headline":"Outline has a rate limit bypass that allows brute force of email login OTP","id":"CVE-2026-33640","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2024-37829","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":8.5,"headline":"Outline 1.6.0 - Unquoted Service Path","id":"CVE-2023-54331","kev_date_added":null,"published":"2026-01-13"},{"cvss_score":8.5,"headline":"Cross-site Scripting (XSS) - Stored in outline/outline","id":"CVE-2023-3532","kev_date_added":null,"published":"2023-07-07"},{"cvss_score":8.1,"headline":"Outline's IDOR allows unauthorized viewing and seizing of private deleted drafts","id":"CVE-2026-24901","kev_date_added":null,"published":"2026-03-17"},{"cvss_score":7.7,"headline":"Outline has IDOR in document share creation that allows unauthorized access to private documents across workspaces","id":"CVE-2026-41649","kev_date_added":null,"published":"2026-04-28"},{"cvss_score":7.6,"headline":"Outline is vulnerable to privilege escalation vulnerability in document sharing","id":"CVE-2025-64487","kev_date_added":null,"published":"2026-02-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-12","vendors":["outline"]},"summary":"Attackers can link victim Outline accounts to attacker Slack identities via unsigned OAuth state, enabling unauthorized access to victim data.","url":"https://insights.sbomify.com/CVE-2026-44695/"}