Vulnerability in Getoutline (CVE-2026-41649)
Summary
Vulnerability in Getoutline (CVE-2026-41649). Confidential information can be exposed externally. Exploitable via shares.create.
Original description
The description as published by the source.
Outline is a service that allows for collaborative documentation. The shares.create API endpoint starting in version 0.86.0 and prior to version 1.7.0 has an insecure direct object reference.. When both collectionId and documentId are provided in the request, the authorization logic only checks access to the collection, completely ignoring the document. This allows an authenticated attacker to generate a valid public share link for any document on the platform, including documents belonging to other workspaces. The full document contents can then be retrieved via the documents.info endpoint. Version 1.7.0 contains a patch.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41649 has been found in Getoutline.
Attackers can target a specific entry point like shares.create over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Getoutline CVE-2026-41649" on the vendor's site.
CVE-2026-41649 (Getoutline) — CWE-639 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: shares.create / collectionId / documentId / documents.info
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Getoutline. Attackers reach the vulnerable code path via shares.create.
Check the vendor advisory for the affected versions of Getoutline. Attack surface: shares.create / collectionId / documentId / documents.info.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Getoutline' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Getoutline' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Getoutlineを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com