{"api_version":"1","generated_at":"2026-08-22T01:52:01+00:00","cve":"CVE-2026-55168","urls":{"html":"https://cve.report/CVE-2026-55168","api":"https://cve.report/api/cve/CVE-2026-55168.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-55168","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-55168"},"summary":{"title":"Runtipi: Authenticated arbitrary file write via backup restore symlink planting","description":"Runtipi is a personal homeserver orchestrator. In 4.10.0 and earlier, Runtipi accepts symbolic links from an attacker-controlled backup archive and copies them into live application paths during the backup restore flow. An authenticated attacker can plant user-config/app.env as a symlink to an arbitrary reachable path and then send PUT /api/user-config/demoapp3:_user with attacker-controlled appEnv content. FilesystemService.writeTextFile() follows the planted link, allowing content to be written outside the intended restore and user-config directory boundary with Runtipi process permissions. This issue is fixed in version 4.10.1.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-08-21 21:17:00","updated_at":"2026-08-21 21:17:00"},"problem_types":["CWE-59","CWE-61","CWE-59 CWE-59: Improper Link Resolution Before File Access ('Link Following')","CWE-61 CWE-61: UNIX Symbolic Link (Symlink) Following"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"HIGH","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"6.5","severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"HIGH","privilegesRequired":"HIGH","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://github.com/runtipi/runtipi/releases/tag/v4.10.1","name":"https://github.com/runtipi/runtipi/releases/tag/v4.10.1","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/runtipi/runtipi/pull/2606","name":"https://github.com/runtipi/runtipi/pull/2606","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/runtipi/runtipi/security/advisories/GHSA-wcrf-g9p9-2wg7","name":"https://github.com/runtipi/runtipi/security/advisories/GHSA-wcrf-g9p9-2wg7","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/runtipi/runtipi/commit/df529a211b05f3a0007b209b6c337f8c1942619c","name":"https://github.com/runtipi/runtipi/commit/df529a211b05f3a0007b209b6c337f8c1942619c","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-55168","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55168","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"runtipi","product":"runtipi","version":"affected < 4.10.1","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"runtipi","vendor":"runtipi","versions":[{"status":"affected","version":"< 4.10.1"}]}],"descriptions":[{"lang":"en","value":"Runtipi is a personal homeserver orchestrator. In 4.10.0 and earlier, Runtipi accepts symbolic links from an attacker-controlled backup archive and copies them into live application paths during the backup restore flow. An authenticated attacker can plant user-config/app.env as a symlink to an arbitrary reachable path and then send PUT /api/user-config/demoapp3:_user with attacker-controlled appEnv content. FilesystemService.writeTextFile() follows the planted link, allowing content to be written outside the intended restore and user-config directory boundary with Runtipi process permissions. This issue is fixed in version 4.10.1."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"HIGH","privilegesRequired":"HIGH","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-59","description":"CWE-59: Improper Link Resolution Before File Access ('Link Following')","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-61","description":"CWE-61: UNIX Symbolic Link (Symlink) Following","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-08-21T20:31:38.124Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/runtipi/runtipi/security/advisories/GHSA-wcrf-g9p9-2wg7","tags":["x_refsource_CONFIRM"],"url":"https://github.com/runtipi/runtipi/security/advisories/GHSA-wcrf-g9p9-2wg7"},{"name":"https://github.com/runtipi/runtipi/pull/2606","tags":["x_refsource_MISC"],"url":"https://github.com/runtipi/runtipi/pull/2606"},{"name":"https://github.com/runtipi/runtipi/commit/df529a211b05f3a0007b209b6c337f8c1942619c","tags":["x_refsource_MISC"],"url":"https://github.com/runtipi/runtipi/commit/df529a211b05f3a0007b209b6c337f8c1942619c"},{"name":"https://github.com/runtipi/runtipi/releases/tag/v4.10.1","tags":["x_refsource_MISC"],"url":"https://github.com/runtipi/runtipi/releases/tag/v4.10.1"}],"source":{"advisory":"GHSA-wcrf-g9p9-2wg7","discovery":"UNKNOWN"},"title":"Runtipi: Authenticated arbitrary file write via backup restore symlink planting"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-55168","datePublished":"2026-08-21T20:31:38.124Z","dateReserved":"2026-06-16T15:13:28.166Z","dateUpdated":"2026-08-21T20:31:38.124Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-21 21:17:00","lastModifiedDate":"2026-08-21 21:17:00","problem_types":["CWE-59","CWE-61","CWE-59 CWE-59: Improper Link Resolution Before File Access ('Link Following')","CWE-61 CWE-61: UNIX Symbolic Link (Symlink) Following"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","baseScore":6.5,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"HIGH","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.2,"impactScore":5.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"55168","Ordinal":"1","Title":"Runtipi: Authenticated arbitrary file write via backup restore s","CVE":"CVE-2026-55168","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"55168","Ordinal":"1","NoteData":"Runtipi is a personal homeserver orchestrator. In 4.10.0 and earlier, Runtipi accepts symbolic links from an attacker-controlled backup archive and copies them into live application paths during the backup restore flow. An authenticated attacker can plant user-config/app.env as a symlink to an arbitrary reachable path and then send PUT /api/user-config/demoapp3:_user with attacker-controlled appEnv content. FilesystemService.writeTextFile() follows the planted link, allowing content to be written outside the intended restore and user-config directory boundary with Runtipi process permissions. This issue is fixed in version 4.10.1.","Type":"Description","Title":"Runtipi: Authenticated arbitrary file write via backup restore s"}]}}}