dbcve.org
RuntipiApplication

CVE-2026-31881

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 4.8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
Runtipi is a personal homeserver orchestrator. Prior to 4.8.0, an unauthenticated attacker can reset the operator (admin) password when a password-reset request is active, resulting in full account takeover. The endpoint POST /api/auth/reset-password is exposed without authentication/authorization checks. During the 15-minute reset window, any remote user can set a new operator password and log in as admin. This vulnerability is fixed in 4.8.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 confidence

The Runtipi homeserver orchestrator prior to version 4.8.0 has an unauthenticated password reset vulnerability. The POST /api/auth/reset-password endpoint lacks authentication and authorization checks, allowing any remote attacker to set a new operator (admin) password during the 15-minute reset window, resulting in full account takeover.

MitigationUpgrade to Runtipi version 4.8.0 or later which includes proper authentication checks on the password reset endpoint. If immediate upgrade is not feasible, monitor for unauthorized password reset activity and consider restricting network access to the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RuntipiApplication
Affected:< 4.8.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Runtipi installation method
    Determine if Runtipi is running via Docker (docker ps), a package manager, or manual installation to locate version information
    Affected if Unable to determine version or version is < 4.8.0
  2. Locate and read the Runtipi version file
    Common locations include: package.json in the installation directory, a VERSION file, or the container image tag. Run 'docker ps' to find the container and 'docker inspect <container>' to check image tags
    Affected if Installed version is < 4.8.0
  3. Verify the reset-password endpoint is network-accessible
    Check if port 3000 (default) or the configured HTTP port is exposed externally. Review reverse proxy configurations (nginx, caddy, etc) for routes to /api/auth/reset-password
    Affected if The /api/auth/reset-password endpoint is reachable from untrusted networks without authentication
  4. Check for recent password reset activity
    Review server logs, authentication logs, or audit trails for POST requests to /api/auth/reset-password that occurred outside of legitimate administrator actions
    Affected if There are unauthenticated POST requests to reset-password in the logs

The environment is affected if Runtipi version is below 4.8.0 and the reset-password endpoint at /api/auth/reset-password is exposed to the network without authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.8.0 or later
Fixed in 4.8.0
Interim mitigation

Upgrade to Runtipi version 4.8.0 or later which includes proper authentication checks on the password reset endpoint. If immediate upgrade is not feasible, monitor for unauthorized password reset activity and consider restricting network access to the application.

Recommended fix High confidence

4.8.0

  1. Upgrade Runtipi to version 4.8.0 or later
  2. After upgrade, verify the /api/auth/reset-password endpoint now requires authentication
  3. Confirm that operator (admin) account can only be reset by authenticated users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Runtipi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31881 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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