Vulnerability in pycti (CVE-2026-44730)
Summary
Vulnerability in pycti (CVE-2026-44730). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.9.7 or later.
Original description
The description as published by the source.
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 6.9.7, an organization admin can escalate their privileges by adding a user from a different organization with higher privileges, to their own organization. This is due to incorrect ACL on userEdit relationAdd. This vulnerability is fixed in 6.9.7.
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-44730 has been found in pycti.
Successful exploitation can lead to full system takeover. CVSS score: 7.2/10.
What to do: upgrade pycti to 6.9.7 or later.
If unsure, ask your IT team or search "pycti CVE-2026-44730" on the vendor's site.
CVE-2026-44730 (pycti) — CWE-284 / CVSS v3 7.2
Attack vector: remote (network-reachable) / no user interaction
Patched: 6.9.7 — 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-284) exists in pycti.
Check the vendor advisory for the affected versions of pycti.
Severity: High (CVSS 7.2/10). Successful exploitation can lead to full system takeover.
Update to 6.9.7.
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 'pycti' . 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 'pycti' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pyctiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade pycti to 6.9.7ステージング環境で 6.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com