# CVE-2026-24129: Runtipi is Vulnerable to Authenticated Arbitrary Remote Code Execution

> Authenticated attackers can execute arbitrary system commands on the host by injecting shell metacharacters into backup filenames during restore operations.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 23 Jan 2026
- **Also known as:** GHSA-vrgf-rcj5-6gv9

## What is CVE-2026-24129?

CVE-2026-24129 is a high-severity command injection vulnerability in runtipi, published on 22 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Runtipi is a Docker-based, personal homeserver orchestrator that facilitates multiple services on a single server. Versions 3.7.0 and above allow an authenticated user to execute arbitrary system commands on the host server by injecting shell metacharacters into backup filenames. The BackupManager fails to sanitize the filenames of uploaded backups. The system persists user-uploaded files directly to the host filesystem using the raw originalname provided in the request. This allows an attacker to stage a file containing shell metacharacters (e.g., $(id).tar.gz) at a predictable path, which is later referenced during the restore process. The successful storage of the file is what allows the subsequent restore command to reference and execute it. This issue has been fixed in version 4.7.0.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Runtipi Runtipi.

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

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

## Is CVE-2026-24129 being exploited?

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

## Other vulnerabilities in runtipi

- [CVE-2026-32729](https://insights.sbomify.com/CVE-2026-32729/): Runtipi has a TOTP two-factor authentication bypass via unrestricted brute-force on `/api/auth/verify-totp` (high 8.1)
- [CVE-2026-31881](https://insights.sbomify.com/CVE-2026-31881/): Runtipi unauthenticated /api/auth/reset-password allows operator account takeover during active reset window (high 7.7)
- [CVE-2026-25116](https://insights.sbomify.com/CVE-2026-25116/): Runtipi vulnerable to unauthenticated docker-compose.yml Overwrite via Path Traversal (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24129 is a high-severity command injection vulnerability in runtipi, published on 22 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24129 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-24129/ (Markdown: https://insights.sbomify.com/CVE-2026-24129/index.md)
```

## Sources

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

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