← Back
CVE-2026-27960
critical
CVSS 9.8
Authentication Bypass in pycti (CVE-2026-27960)
Summary
authentication bypass in pycti (CVE-2026-27960). Successful exploitation can lead to full system takeover. Exploitable via ``APP__ADMIN__EXTERNALLY_MANAGED``. Mitigation: upgrade to `6.9.13` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27960** has been found in pycti.
Attackers can target a specific entry point like ``APP__ADMIN__EXTERNALLY_MANAGED`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade pycti to **6.9.13** or later.
If unsure, ask your IT team or search "pycti CVE-2026-27960" on the vendor's site.
CVE-2026-27960 (pycti) — CWE-287 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `APP__ADMIN__EXTERNALLY_MANAGED`
Patched: `6.9.13` — 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.
❓ What is the problem
**authentication bypass** (CWE-287) exists in pycti. Attackers reach the vulnerable code path via ``APP__ADMIN__EXTERNALLY_MANAGED`` without authentication.
📍 Affected scope
pycti — . Attack surface: `APP__ADMIN__EXTERNALLY_MANAGED`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **6.9.13**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pycti' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pycti' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pycti` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pycti to 6.9.13ステージング環境で 6.9.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pycti
[{"type":"ECOSYSTEM","events":[{"introduced":"6.9.0"},{"fixed":"6.9.13"}]}]