CVE-2026-30958

OneUptime: Path Traversal — Arbitrary File Read (No Auth)

Published Mar 10, 2026 CVSS 3.1 · 7.2 High EPSS 1.2% KEV · Not listed
Description
OneUptime is a solution for monitoring and managing online services. Prior to 10.0.21, an unauthenticated path traversal in the /workflow/docs/:componentName endpoint allows reading arbitrary files from the server filesystem. The componentName route parameter is concatenated directly into a file path passed to res.sendFile() in orker/FeatureSet/Workflow/Index.ts with no sanitization or authentication middleware. This vulnerability is fixed in 10.0.21.

Analysis

AI-generated

Technical impact

This vulnerability is a path traversal flaw in the /workflow/docs/:componentName endpoint of OneUptime. An attacker can supply a specially crafted componentName value that, after concatenation into a file system path, bypasses the intended directory boundaries. The flaw allows reading any file accessible by the running process, including configuration files, secrets, and potentially sensitive data. Because no authentication checks are performed, any network user can exploit the flaw without credentials, leading to a high risk of data exposure.

Affected Systems

Affected are installations of OneUptime version prior to 10.0.21, with a componentName route that feeds directly into res.sendFile(). The vulnerability applies to all vendors or products named OneUptime:oneuptime, encompassing any deployment of the open‑source monitoring platform.

Risk and Exploitability

The CVSS score of 7.2 indicates a high severity, and although the EPSS score is below 1 %, the absence of a KEV listing does not diminish the potential impact. The lack of authentication makes the attack vector trivial for an external actor with network access to the endpoint. The exploit requires only a HTTP request, no special privileges, and can be performed by modifying the path segments or using relative directory references. Once triggered, the attacker obtains arbitrary filesystem content.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OneUptime to version 10.0.21 or later, which sanitizes the componentName input and removes the vulnerable endpoint logic.
  • Configure the reverse‑proxy or firewall to deny unauthenticated access to the /workflow/docs/ endpoint, ensuring that only authorized users can reach it.
  • Continuously monitor web server logs for path traversal patterns, such as repeated attempts to access hidden or system files, and investigate promptly.

Generated by OpenCVE AI on April 16, 2026 at 09:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Hackerbay
Hackerbay oneuptime
CPEs cpe:2.3:a:hackerbay:oneuptime:*:*:*:*:*:*:*:*
Vendors & Products Hackerbay
Hackerbay oneuptime
Type Values Removed Values Added
First Time appeared Oneuptime
Oneuptime oneuptime
Vendors & Products Oneuptime
Oneuptime oneuptime
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description OneUptime is a solution for monitoring and managing online services. Prior to 10.0.21, an unauthenticated path traversal in the /workflow/docs/:componentName endpoint allows reading arbitrary files from the server filesystem. The componentName route parameter is concatenated directly into a file path passed to res.sendFile() in orker/FeatureSet/Workflow/Index.ts with no sanitization or authentication middleware. This vulnerability is fixed in 10.0.21.
Title OneUptime: Path Traversal — Arbitrary File Read (No Auth)
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}

Weaknesses
  • CWE-22

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

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 10, 2026, 5:31 PM
Reserved
Mar 7, 2026, 5:34 PM
Status
Analyzed
Published
Mar 10, 2026, 6:18 PM
Modified
Oct 7, 2026, 8:10 AM