/

CVE-2026-31881

Severity:

HIGH RISK

(7.7)

Missing Authentication in Runtipi Homeserver Orchestrator

CVE-2026-31881

Analyzed

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Account Takeover / Privilege Escalation to Administrator

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authentication check in Runtipi's password reset flow allows any remote user to reset the operator (admin) password while a reset request is active.

During the 15-minute reset window, an attacker can call the exposed password reset endpoint and set a new operator password, leading to full administrative account takeover.

Affected context

This vulnerability arises in Runtipi deployments where the password reset functionality is enabled and reachable over the network.

The issue occurs in the /api/auth/reset-password endpoint, which processes active password reset requests without enforcing authentication or authorization.

As long as a legitimate password reset has been initiated and is within the 15-minute validity window, any remote user who can reach the API can attempt to set a new operator (admin) password.

Exploit preconditions

  • Attack surface: Public or internal HTTP(S) interface exposing the Runtipi API.
  • Required access: Network-level access to the Runtipi instance; no prior authentication required.
  • Trigger point: An operator-initiated password reset request is active within its 15-minute window.
  • Why exploitation is possible: The POST /api/auth/reset-password endpoint accepts password change requests tied to an active reset flow but does not validate the caller's identity or enforce a binding between the reset request and the requester, violating authentication and authorization expectations.

Why this happens

The core issue is a missing authentication and authorization check on a sensitive operation: resetting the administrator password.

Instead of requiring a verified identity, a signed token, or another strong binding to the original reset requester, the application exposes POST /api/auth/reset-password in a way that trusts any incoming request during the reset window.

This fits CWE-306: Missing Authentication for Critical Function, where a security-critical endpoint (password reset finalize) is callable by unauthenticated users.

Conceptually, the design treats the existence of an active reset request as sufficient proof of legitimacy, without verifying that the actor completing the reset is the intended account owner.

Potential impact

  • Remote attackers can set a new operator (admin) password during an active reset window.
  • Full administrative account takeover of the Runtipi instance.
  • Unauthorized access to management functions, configuration, and hosted services.
  • Potential modification or deletion of data, applications, or service configurations.
  • Use of the compromised instance as a pivot point for further attacks within the local network.

General mitigation guidance

Effective mitigation typically involves strengthening the authentication and binding for password reset flows and tightening access to critical endpoints.

Pattern-based improvements include:

  • Requiring a cryptographically strong, single-use reset token tied to the specific account and reset request, and validating it on the reset endpoint.
  • Ensuring that password reset completion endpoints are protected by strict checks (e.g., token presence, expiry, and integrity), and cannot be invoked without valid proof of possession.
  • Making reset tokens unguessable and bound to the communication channel (e.g., delivered via email or other out-of-band mechanism only reachable by the legitimate operator).
  • Implementing short-lived, single-use tokens that are invalidated immediately after successful password change.
  • Applying rate limiting and logging for password reset operations to reduce automated abuse and aid in incident response.
  • Designing the reset flow so that sensitive endpoints never rely solely on a time window but always enforce a strong verifier associated with the rightful account owner.

How teams detect issues like this

Detection focuses on identifying unauthenticated access paths to critical security functions and validating reset flow design.

Useful approaches include:

  • Static analysis and API review to flag password-reset and authentication-related endpoints that lack middleware or decorators enforcing authentication/authorization.
  • Configuration and routing inspections to confirm that sensitive routes (e.g., /api/auth/reset-password) are consistently protected by the same security layers as other account-modifying operations.
  • Code review checklists that explicitly call out password reset initiation and completion steps, verifying use of strong, scoped tokens and proper expiry handling.
  • Runtime monitoring and logs analysis to spot anomalous patterns, such as multiple password resets from unfamiliar IPs or unauthenticated requests invoking high-impact endpoints.
  • Integrating automated security testing tools that crawl APIs and highlight state-changing endpoints reachable without authentication.

Sources

SourceLink
github.comgithub.com/runtipi/runtipi/security/advisories/GHSA-96fm-whrc-cwg3

Frequently asked

questions

Yes. Any remote user who can reach the Runtipi API and knows or can guess that a password reset is active during the 15-minute window can exploit the issue; no prior login is required.

The attacker only needs network access to the vulnerable Runtipi instance. They do not need valid credentials, but the exploit window is limited to periods when a legitimate password reset request is active.

Implement a robust password reset flow that requires a strong, single-use reset token securely delivered to the legitimate operator, and ensure the reset-password endpoint validates this token (and its expiry) before allowing a password change.

Treat all security-sensitive endpoints—especially those related to authentication and password management—as privileged operations that must be guarded by explicit authentication and authorization checks, incorporate secure reset-token design, and enforce these patterns via code review standards and automated tests.

Find out what's already
exploitable in your codebase.