CVE-2026-47277
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRuntipi 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRuntipi versions 4.9.1-4.9.3 have an unauthenticated arbitrary file read vulnerability in the logo serving endpoint. The endpoint uses a path guard that only checks the lexical path without resolving symlinks, allowing attackers to create malicious symlinks in cloned app-store repositories that point to sensitive files outside the repository (e.g., /data/.env, /data/state/seed), exposing JWT secrets and credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Runtipi versionCheck the version of your Runtipi installation. This is typically visible in the Runtipi dashboard UI, or can be found in the container/host system running Runtipi (check the application logs, docker labels, or configuration files).Affected if The installed version is 4.9.1, 4.9.2, or 4.9.3 (any version from 4.9.1 through 4.9.3 inclusive).
-
Locate app-store repositoriesIdentify the directory where app-store repositories are cloned. This is typically under the Runtipi data directory (often /data or a mounted volume). Look for folders containing cloned application repositories that were cloned from the Runtipi app-store.Affected if You have one or more cloned app-store repositories present on the system.
-
Scan for symlinks pointing outside repositoriesIn each cloned app-store repository directory, search for symbolic links. Use commands like 'find /path/to/appstore -type l -ls' or manually inspect repository folders for symlink files. Verify the target of each symlink by checking if it points to a path outside its own repository directory (e.g., a symlink in an app folder pointing to /data/ or other absolute paths).Affected if Any symlink exists within an app-store repository that points to a path outside that repository's directory, particularly to /data/, /data/.env, or /data/state/seed.
-
Test unauthenticated logo endpoint accessIf your Runtipi instance is running, attempt to access the logo serving endpoint without authentication. Based on typical Runtipi endpoints, this may be at a URL path like /api/apps/logo or similar. Use a web browser or curl command to request a known file path via this endpoint.Affected if The logo endpoint is accessible without authentication and accepts a filename parameter that can be manipulated to traverse paths.
You are affected if your Runtipi version is between 4.9.1 and 4.9.3 inclusive AND the unauthenticated logo endpoint is accessible AND malicious symlinks exist in your cloned app-store repositories pointing to sensitive files outside those repositories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Runtipi 4.10.0 or later to patch the vulnerability. If immediate upgrade is not possible, restrict access to the unauthenticated logo endpoint and audit cloned app-store repositories for malicious symlinks.
4.10.0
- Upgrade Runtipi from version 4.9.1, 4.9.2, or 4.9.3 to version 4.10.0 or later to remediate the path traversal vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47277 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data