{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-55439", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-06-16T21:59:57.017Z", "datePublished": "2026-06-25T15:57:08.639Z", "dateUpdated": "2026-06-25T15:57:08.639Z"}, "containers": {"cna": {"title": "Halo: Path Traversal in Backup Download Leads to Arbitrary File Read", "problemTypes": [{"descriptions": [{"cweId": "CWE-22", "lang": "en", "description": "CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "LOW", "baseScore": 5.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "HIGH", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:L", "version": "3.1"}}], "references": [{"name": "https://github.com/halo-dev/halo/security/advisories/GHSA-h8wj-chr2-hf66", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/halo-dev/halo/security/advisories/GHSA-h8wj-chr2-hf66"}, {"name": "https://github.com/halo-dev/halo/issues/10064", "tags": ["x_refsource_MISC"], "url": "https://github.com/halo-dev/halo/issues/10064"}], "affected": [{"vendor": "halo-dev", "product": "halo", "versions": [{"version": "< 2.24.3", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-06-25T15:57:08.639Z"}, "descriptions": [{"lang": "en", "value": "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": {"advisory": "GHSA-h8wj-chr2-hf66", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{}