CVE-2026-34759 Missing authorization in oneuptime

Critical 9.2 Published 2 Apr 2026 Updated 3 Apr 2026

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

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

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

Which versions are affected by CVE-2026-34759?

It affects 1 product.

Products include 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.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-34759 being exploited?

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

Sources

Also known as GHSA-6wc5-rhvj-cx7f.