{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55168 exists.","fix":"No fix has been published for CVE-2026-55168 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55168 is a medium-severity path traversal vulnerability in runtipi, published on 21 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55168 and fix it if it is affected.\n\nWhat it is: CVE-2026-55168 is a medium-severity path traversal vulnerability in runtipi, published on 21 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55168 exists.\n\nAffected product: runtipi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55168/ (Markdown: https://insights.sbomify.com/CVE-2026-55168/index.md)","id":"CVE-2026-55168","markdown":"https://insights.sbomify.com/CVE-2026-55168/index.md","name":"CVE-2026-55168","record":{"aliases":["GHSA-wcrf-g9p9-2wg7"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Homeserver orchestrator","requires_auth":"high_privilege","summary":"An authenticated attacker can exploit symlink handling in backup restore to write arbitrary files, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-16T17:35:30Z","kind":"github_poc","ref":"https://github.com/KovachVL/CVE-2026-55168","stars":0,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"Runtipi: Authenticated arbitrary file write via backup restore symlink planting","id":"CVE-2026-55168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OpenFGA MySQL backend: case-insensitive collation on identifier columns causes incorrect authorization decisions","id":"CVE-2026-55170"},"packages":[],"prev":{"headline":"LDAP Account Manager: WebAuthn authentication challenge is kept in the PHP session","id":"CVE-2026-55167"},"products":["runtipi"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-25","vendors":["runtipi"]},"summary":"An authenticated attacker can exploit symlink handling in backup restore to write arbitrary files, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-55168/"}