Vulnerability in Runtipi is a personal homeserver orchestrator. In (CVE-2026-55168)
Summary
Vulnerability in Runtipi is a personal homeserver orchestrator. In (CVE-2026-55168). Data can be tampered with by attackers. Exploitable via PUT /api/user-config/demoapp3.
Original description
The description as published by the source.
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.
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-55168 has been found in Runtipi is a personal homeserver orchestrator. In.
Attackers can target a specific entry point like PUT /api/user-config/demoapp3 over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Runtipi is a personal homeserver orchestrator. In CVE-2026-55168" on the vendor's site.
CVE-2026-55168 (Runtipi is a personal homeserver orchestrator. In) — CWE-59 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/user-config/demoapp3
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-59) exists in Runtipi is a personal homeserver orchestrator. In. Attackers reach the vulnerable code path via PUT /api/user-config/demoapp3.
Check the vendor advisory for the affected versions of Runtipi is a personal homeserver orchestrator. In. Attack surface: PUT /api/user-config/demoapp3.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
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/user-config/demoapp3 requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Runtipi is a personal homeserver orchestrator. In を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /api/user-config/demoapp3' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/user-config/demoapp3への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /api/user-config/demoapp3 on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。