OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header that leads to cross‑tenant data ex

Description

A low‑privileged user can bypass authorization and tenant isolation in OneUptime v10.0.20 by sending a forged is-multi-tenant-query header together with a controlled projectid header.

Because the server trusts this client-supplied header, internal permission checks in BasePermission are skipped and tenant scoping is disabled.

Recommendation

Update the @oneuptime/common package to the latest compatible version. Followings are version details:

• Affected version(s): < 10.0.21
• Patched version(s): 10.0.21

References

• GHSA-r5v6-2599-9g3m
• CVE-2026-30956
• CWE-285
• CWE-862
• CAPEC-310
• OWASP 2021-A1
• OWASP 2021-A6

Related Issues

• Axios has a Patch Bypass: Proxy-Authorization Header Injection via Prototype Pollution — Incomplete Null-Prototype Fix - CVE-2026-44489
• OneUptime has WebAuthn 2FA bypass: server accepts client-supplied challenge instead of server-stored value, allowing cre - CVE-2026-28787
• OneUptime has WhatsApp Resend Verification Authorization Bypass - CVE-2026-30959
• StudioCMS has Authorization Bypass Through User-Controlled Key - CVE-2026-24134

You might also like:

Apache and Express Path Traversal plus Nginx Restriction Bypass Tests with SmartScanner

10 Secure Coding Best Practices to Follow in Every Project

Update Cheat Sheet for Developers

Tags:

npm

@oneuptime/common