Vulnerability in Ghostfolio (CVE-2026-59709)
Summary
Vulnerability in Ghostfolio (CVE-2026-59709). Risk of unauthorized operations or information disclosure. Exploitable via PUT /api/v1/portfolio/holding/.
Original description
The description as published by the source.
Ghostfolio's PUT /api/v1/portfolio/holding/:dataSource/:symbol/tags endpoint fails to verify Access.permissions field when processing the Impersonation-Id header, allowing read-only access grantees to modify portfolio holding tags. Attackers with valid read-only share tokens can assign or remove tags on victim holdings, corrupting portfolio categorization and reports.
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-59709 has been found in Ghostfolio.
Attackers can target a specific entry point like PUT /api/v1/portfolio/holding/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Ghostfolio CVE-2026-59709" on the vendor's site.
CVE-2026-59709 (Ghostfolio) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/v1/portfolio/holding/
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 Ghostfolio. Attackers reach the vulnerable code path via PUT /api/v1/portfolio/holding/.
Check the vendor advisory for the affected versions of Ghostfolio. Attack surface: PUT /api/v1/portfolio/holding/.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
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 PUT /api/v1/portfolio/holding/ requests with malformed payloads or SQL meta-characters. Run grep -r 'Ghostfolio' . 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 'Ghostfolio' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Ghostfolioを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PUT /api/v1/portfolio/holding/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/v1/portfolio/holding/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /api/v1/portfolio/holding/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- report github.com
- web github.com