Vulnerability in Genealogy (CVE-2026-39355)
Summary
Vulnerability in Genealogy (CVE-2026-39355). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.9.1 or later.
Original description
The description as published by the source.
Genealogy is a family tree PHP application. Prior to 5.9.1, a critical broken access control vulnerability in the genealogy application allows any authenticated user to transfer ownership of arbitrary non-personal teams to themselves. This enables complete takeover of other users’ team workspaces and unrestricted access to all genealogy data associated with the compromised team. This vulnerability is fixed in 5.9.1.
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-39355 has been found in Genealogy.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade Genealogy to 5.9.1 or later.
If unsure, ask your IT team or search "Genealogy CVE-2026-39355" on the vendor's site.
CVE-2026-39355 (Genealogy) — CWE-862 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.9.1 — 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-862) exists in Genealogy.
Check the vendor advisory for the affected versions of Genealogy.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 5.9.1.
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 'Genealogy' . 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 'Genealogy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Genealogyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Genealogy to 5.9.1ステージング環境で 5.9.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov