Path Traversal in Halo (CVE-2026-55439)
Summary
Path traversal in Halo (CVE-2026-55439). Confidential information can be exposed externally. Exploitable via GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename}. Mitigation: upgrade to 2.24.3 or later.
Original description
The description as published by the source.
Halo is an open source website building tool. Prior to 2.24.3, a path traversal vulnerability in the backup download endpoint allows authenticated administrators to read arbitrary files from the server filesystem. The backup download endpoint (GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename}) in MigrationServiceImpl.download() resolves the backup filename via Path.resolve() without validating that the resolved path stays within the designated backups directory. Also, the Backup creation endpoint (POST /apis/migration.halo.run/v1alpha1/backups) does not sanitize the status fields during creation This vulnerability is fixed in 2.24.3.
Source: NIST National Vulnerability Database NVD
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-55439 has been found in Halo.
Attackers can target a specific entry point like GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade Halo to 2.24.3 or later.
If unsure, ask your IT team or search "Halo CVE-2026-55439" on the vendor's site.
CVE-2026-55439 (Halo) — CWE-22 / CVSS v3 5.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename} / POST /apis/migration.halo.run/v1alpha1/backups
Patched: 2.24.3 — 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.
Path traversal (CWE-22) exists in Halo. Attackers reach the vulnerable code path via GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename}.
Check the vendor advisory for the affected versions of Halo. Attack surface: GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename} / POST /apis/migration.halo.run/v1alpha1/backups.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 2.24.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename} requests with malformed payloads or SQL meta-characters. Run grep -r 'Halo' . 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 'Halo' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Haloを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Halo to 2.24.3ステージング環境で 2.24.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /apis/console.api.migration.halo.run/v1alpha1/backups/{name}/files/{filename} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。