# CVE-2026-34759: Missing authorization in oneuptime

> Unauthenticated attackers can access notification APIs to purchase phone numbers and delete alerts, causing financial abuse and service disruption.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-6wc5-rhvj-cx7f

## What is CVE-2026-34759?

CVE-2026-34759 is a critical missing authorization vulnerability in oneuptime, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OneUptime is an open-source monitoring and observability platform. Prior to version 10.0.42, multiple notification API endpoints are registered without authentication middleware, while sibling endpoints in the same codebase correctly use ClusterKeyAuthorization.isAuthorizedServiceMiddleware. These endpoints are externally reachable via the Nginx proxy at /notification/. Combined with a projectId leak from the public Status Page API, an unauthenticated attacker can purchase phone numbers on the victim's Twilio account and delete all existing alerting numbers. This issue has been patched in version 10.0.42.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Hackerbay Oneuptime.

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

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

## Is CVE-2026-34759 being exploited?

There is no known exploitation of CVE-2026-34759 in the wild and no public exploit code.

## 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-34759 and fix it if it is affected.

What it is: CVE-2026-34759 is a critical missing authorization vulnerability in oneuptime, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34759 in the wild and no public exploit code.

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

## Sources

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

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