Privilege Escalation in Outline (CVE-2026-43886)
Summary
Vulnerability in Outline (CVE-2026-43886). Data can be tampered with by attackers. Mitigation: upgrade to 1.7.0 or later.
Original description
The description as published by the source.
Outline is a service that allows for collaborative documentation. From 0.84.0 to 1.6.1, a logic error in OAuthInterface.validateScope() uses Array.some() to validate requested OAuth scopes, causing the function to accept the entire scope array if any single scope is valid. An attacker can smuggle the wildcard * scope by requesting scope=read *, escalating a read-only OAuth token to full unrestricted API access including write, delete, and admin operations. This vulnerability is fixed in 1.7.0.
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-43886 has been found in Outline.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade Outline to 1.7.0 or later.
If unsure, ask your IT team or search "Outline CVE-2026-43886" on the vendor's site.
CVE-2026-43886 (Outline) — CWE-269 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.7.0 — apply immediately
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-269) exists in Outline.
Check the vendor advisory for the affected versions of Outline.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 1.7.0.
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 'Outline' . 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 'Outline' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Outlineを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Outline to 1.7.0ステージング環境で 1.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov