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 <Signature> 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.
References
| Link | Resource |
|---|---|
| https://github.com/OneUptime/oneuptime/commit/2fd7ede52f60444710628d6c1b34dee2ef9e57d1 | Patch |
| https://github.com/OneUptime/oneuptime/releases/tag/10.0.42 | Product Release Notes |
| https://github.com/OneUptime/oneuptime/security/advisories/GHSA-5w5c-766x-265g | Exploit Mitigation Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-04-02 20:16
Updated : 2026-07-24 21:10
NVD link : CVE-2026-34840
Mitre link : CVE-2026-34840
CVE.ORG link : CVE-2026-34840
JSON object : View
Products Affected
hackerbay
- oneuptime
CWE
CWE-347
Improper Verification of Cryptographic Signature
