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.
Published: 2026-08-21
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Authenticated arbitrary file write
Action: Apply Upgrade
AI Analysis

Impact

In Runtipi versions 4.10.0 and earlier an attacker with authentication can embed symbolic links in a backup archive. During restore the backup handler copies these symlinked paths into the live application directories; the internal FilesystemService.writeTextFile() function follows the link, which allows the attacker to write arbitrary content to a location outside the intended user‑configuration directory. This flaw can be used to overwrite configuration files, place malicious scripts, or otherwise tamper with the host filesystem, potentially leading to privilege escalation or persistent compromise. The weakness is distinctively a path traversal and symlink exploitation, reflected by the associated CWE-59 and CWE-61 identifiers.

Affected Systems

Any instance of Runtipi running version 4.10.0 or earlier is affected; the vulnerability resides in the backup restore flow of these releases.

Risk and Exploitability

The CVSS score of 6.5 marks moderate severity. The EPSS score is not available and the vulnerability is not listed in CISA KEV catalog. Exploitation requires HTTP authentication to access the /api/user‑config endpoint and the ability to trigger a backup restore operation. No additional OS privileges are needed beyond the credentials of the authenticated user. The exploit path is relatively straightforward: a malicious backup archive is uploaded and the symlinked file is written during the restore, enabling arbitrary file write with the permissions of the Runtipi process.

Generated by OpenCVE AI on August 21, 2026 at 22:19 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Runtipi to version 4.10.1 or later, which removes symlink processing in the backup restore flow.
  • If an upgrade is not immediately possible, restrict or disable the backup restore endpoint for authenticated users to prevent symlink planting.
  • Configure the underlying file system or application process to disallow following symlinks when writing files, ensuring any symlink resolution is blocked.

Generated by OpenCVE AI on August 21, 2026 at 22:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 27 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 21 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Runtipi
Runtipi runtipi
Vendors & Products Runtipi
Runtipi runtipi

Fri, 21 Aug 2026 20:45:00 +0000

Type Values Removed Values Added
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.
Title Runtipi: Authenticated arbitrary file write via backup restore symlink planting
Weaknesses CWE-59
CWE-61
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-25T17:01:52.501Z

Reserved: 2026-06-16T15:13:28.166Z

Link: CVE-2026-55168

cve-icon Vulnrichment

Updated: 2026-08-25T17:01:15.851Z

cve-icon NVD

Status : Received

Published: 2026-08-21T21:17:00.410

Modified: 2026-08-25T17:17:30.117

Link: CVE-2026-55168

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T22:30:17Z

Weaknesses
  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')

  • CWE-61

    UNIX Symbolic Link (Symlink) Following