oneuptime up to 10.0.41 API Endpoint /notification/ authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in oneuptime up to 10.0.41. It has been declared as problematic. This issue affects some unknown processing of the file /notification/ of the component API Endpoint. Executing a manipulation can lead to authorization. This vulnerability appears as CVE-2026-34759. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability has been found in oneuptime up to 10.0.41 and classified as problematic. This vulnerability affects some unknown processing of the file /notification/ of the component API Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-34759 since 03/30/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.
Upgrading to version 10.0.42 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 9adbd04538714740506708d6fa610e433be4d2a4 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 10.0.0
- 10.0.1
- 10.0.2
- 10.0.3
- 10.0.4
- 10.0.5
- 10.0.6
- 10.0.7
- 10.0.8
- 10.0.9
- 10.0.10
- 10.0.11
- 10.0.12
- 10.0.13
- 10.0.14
- 10.0.15
- 10.0.16
- 10.0.17
- 10.0.18
- 10.0.19
- 10.0.20
- 10.0.21
- 10.0.22
- 10.0.23
- 10.0.24
- 10.0.25
- 10.0.26
- 10.0.27
- 10.0.28
- 10.0.29
- 10.0.30
- 10.0.31
- 10.0.32
- 10.0.33
- 10.0.34
- 10.0.35
- 10.0.36
- 10.0.37
- 10.0.38
- 10.0.39
- 10.0.40
- 10.0.41
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: oneuptime 10.0.42
Patch: 9adbd04538714740506708d6fa610e433be4d2a4
Timeline
03/30/2026 CVE reserved04/02/2026 Advisory disclosed
04/02/2026 VulDB entry created
04/03/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6wc5-rhvj-cx7f
Status: Confirmed
CVE: CVE-2026-34759 (🔒)
GCVE (CVE): GCVE-0-2026-34759
GCVE (VulDB): GCVE-100-355018
Entry
Created: 04/03/2026 00:02Changes: 04/03/2026 00:02 (70)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.