LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25116: Runtipi vulnerable to unauthenticated docker-compose.yml Overwrite via Path Traversal

Runtipi is a personal homeserver orchestrator. Starting in version 4.5.0 and prior to version 4.7.2, an unauthenticated Path Traversal vulnerability in the `UserConfigController` allows any remote user to overwrite the system's `docker-compose.yml` configuration file. By exploiting insecure URN parsing, an attacker can replace the primary stack configuration with a malicious one, resulting in full Remote Code Execution (RCE) and host filesystem compromise the next time the instance is restarted by the operator. Version 4.7.2 fixes the vulnerability.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-25116 affects Runtipi homeserver instances running versions 4.5.0 before 4.7.2. An unauthenticated remote user can overwrite the main Docker Compose configuration through path traversal. Code execution occurs when the operator next restarts the instance, making this serious for internet-exposed personal or small-business servers.

Executive priority

Prioritize upgrade for any internet-reachable Runtipi instance. The vulnerability can turn a configuration overwrite into host compromise after restart, but public evidence does not show active exploitation. Treat as a high-priority maintenance and exposure-reduction item, especially for systems hosting sensitive files or services.

Technical view

The issue is an unauthenticated path traversal in Runtipi’s UserConfigController caused by insecure URN parsing. It can overwrite docker-compose.yml, enabling attacker-controlled stack configuration and later remote code execution plus host filesystem compromise after operator restart. CVSS is 7.6, with network attack vector, low complexity, no privileges, and user interaction required.

Likely exposure

Exposure is limited to Runtipi deployments on versions 4.5.0 through before 4.7.2. Risk is highest where the Runtipi interface or affected endpoint is reachable from untrusted networks. The provided sources do not identify other affected products or managed service exposure.

Exploitation context

The CVE record and GitHub advisory describe unauthenticated remote overwrite leading to RCE on next restart. CISA KEV status is false in the provided bundle, and no cited source states active exploitation. User interaction is the operator restarting the instance after configuration overwrite.

Researcher notes

The strongest evidence is the GitHub security advisory and v4.7.2 release reference. The attack chain depends on overwriting docker-compose.yml and a later restart. Avoid assuming immediate RCE without restart. No exploit code, indicators, or mass exploitation evidence are included in the provided sources.

Mitigation direction

  • Upgrade Runtipi to version 4.7.2 or later.
  • Do not expose Runtipi administration interfaces to untrusted networks.
  • Before restarting affected systems, inspect docker-compose.yml for unauthorized changes.
  • Restore known-good configuration if tampering is suspected.
  • Check the vendor advisory and release notes for any updated guidance.

Validation and detection

  • Inventory Runtipi instances and record installed versions.
  • Flag versions 4.5.0 through 4.7.1 as affected.
  • Confirm whether Runtipi is reachable from the internet or untrusted networks.
  • Review docker-compose.yml modification history for unexpected changes.
  • Review Runtipi and host logs for suspicious unauthenticated requests.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25116 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2026-25116Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
runtipiruntipi>= 4.5.0, < 4.7.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.