# CVE-2026-30958: OneUptime: Path Traversal — Arbitrary File Read (No Auth)

> Unauthenticated attackers can read arbitrary files from the server filesystem via a path traversal vulnerability in the workflow docs endpoint.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-p2wh-9pw8-hvff

## What is CVE-2026-30958?

CVE-2026-30958 is a high-severity path traversal vulnerability in oneuptime, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Hackerbay Oneuptime.

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

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

## Is CVE-2026-30958 being exploited?

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

Public exploit code:

- OneUptime < 10.0.21 - Path Traversal (nuclei): http/cves/2026/CVE-2026-30958.yaml

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30958 is a high-severity path traversal vulnerability in oneuptime, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30958 exists.

Affected product: oneuptime. 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-30958/ (Markdown: https://insights.sbomify.com/CVE-2026-30958/index.md)
```

## Sources

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

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