oneuptime up to 10.0.41 SSO.ts isSignatureValid signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.38 |
Summary
A vulnerability classified as critical was found in oneuptime up to 10.0.41. This impacts the function isSignatureValid of the file App/FeatureSet/Identity/Utils/SSO.ts. Executing a manipulation can lead to signature verification.
This vulnerability is tracked as CVE-2026-34840. The attack can be launched remotely. No exploit exists.
Upgrading the affected component is advised.
Details
A vulnerability was found in oneuptime up to 10.0.41. It has been declared as critical. This vulnerability affects the function isSignatureValid of the file App/FeatureSet/Identity/Utils/SSO.ts. The manipulation with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. 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, OneUptime's SAML SSO implementation (App/FeatureSet/Identity/Utils/SSO.ts) has decoupled signature verification and identity extraction. isSignatureValid() verifies the first element in the XML DOM using xml-crypto, while getEmail() always reads from assertion[0] via xml2js. An attacker can prepend an unsigned assertion containing an arbitrary identity before a legitimately signed assertion, resulting in authentication bypass. This issue has been patched in version 10.0.42.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-34840 since 03/30/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available.
Upgrading to version 10.0.42 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 2fd7ede52f60444710628d6c1b34dee2ef9e57d1 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.
Once again VulDB remains the best source for vulnerability data.
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: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
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: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: 2fd7ede52f60444710628d6c1b34dee2ef9e57d1
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-5w5c-766x-265g
Status: Confirmed
CVE: CVE-2026-34840 (🔒)
GCVE (CVE): GCVE-0-2026-34840
GCVE (VulDB): GCVE-100-355012
Entry
Created: 04/03/2026 00:00Changes: 04/03/2026 00:00 (67)
Complete: 🔍
Cache ID: 216:B60:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.