OneUptime has WebAuthn 2FA bypass: server accepts client-supplied challenge instead of server-stored value, allowing credential replay
Description
OneUptime is a solution for monitoring and managing online services. In version 10.0.11 and prior, the WebAuthn authentication implementation does not store the challenge on the server side. Instead, the challenge is returned to the client and accepted back from the client request body during verification. This violates the WebAuthn specification (W3C Web Authentication Level 2, §13.4.3) and allows an attacker who has obtained a valid WebAuthn assertion (e.g., via XSS, MitM, or log exposure) to replay it indefinitely, completely bypassing the second-factor authentication. No known patches are available.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
@oneuptime/commonnpm | <= 10.0.11 | — |
Affected products
2- OneUptime/oneuptimev5Range: <= 10.0.11
Patches
Vulnerability mechanics
References
3- github.com/advisories/GHSA-gjjc-pcwp-c74mghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-28787ghsaADVISORY
- github.com/OneUptime/oneuptime/security/advisories/GHSA-gjjc-pcwp-c74mghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.