# CVE-2026-47277: Runtipi: Unauthenticated arbitrary file read through app-store logo symlinks

> Unauthenticated attackers can read arbitrary local files via symlinked app-store logos, exposing secrets and configuration in Runtipi instances.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-qrqj-p7hm-4m66

## What is CVE-2026-47277?

CVE-2026-47277 is a medium-severity path traversal vulnerability in runtipi, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Runtipi is a personal homeserver orchestrator. In versions 4.9.1 through 4.9.3, Runtipi serves marketplace app logos from files inside cloned app-store repositories through an unauthenticated endpoint, which leads to arbitrary file read through app-store logo symlinks. The path guard checks only the lexical path before Node reads the file, so a Git app store that contains metadata/logo.jpg as a symbolic link can cause Runtipi to read and return the symlink target. Because the endpoint is public and the symlink target may point outside the cloned repository, this can expose local files from the Runtipi container such as /data/.env, /data/state/seed, logs, or application files. This can disclose JWT secrets, service credentials, local configuration, and operational logs depending on the instance. The issue has been fixed in version 4.10.0.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-47277?


## How do I fix CVE-2026-47277?

No fix has been published for CVE-2026-47277 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47277 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47277 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47277 and fix it if it is affected.

What it is: CVE-2026-47277 is a medium-severity path traversal vulnerability in runtipi, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47277 exists.

Affected product: runtipi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47277/ (Markdown: https://insights.sbomify.com/CVE-2026-47277/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47277
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47277
- OSV: https://osv.dev/vulnerability/CVE-2026-47277

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47277/
Summaries are generated and may contain mistakes; the official description above is the record.