Is CVE-2026-30956 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-30956 being exploited in the wild.

How severe is CVE-2026-30956?

Critical severity, with a CVSS score of 9.9, published 10 March 2026.

Which products and versions are affected?

@oneuptime/common (npm) SEMVER:introduced=0,fixed=10.0.21; OneUptime < 10.0.21.

Is there a fix for CVE-2026-30956?

Yes. @oneuptime/common (npm): upgrade to 10.0.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-30956 attacked?

It is attacked over the network.

Am I affected by CVE-2026-30956?

Check whether you run Hackerbay Oneuptime, @oneuptime/common (npm) or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-30956: OneUptime authorization bypass via is-multi-tenant-query header

Q: Is there a fix for CVE-2026-30956?

Yes. @oneuptime/common (npm): upgrade to 10.0.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-30956 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-30956?

Check whether you run Hackerbay Oneuptime, @oneuptime/common (npm) or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-30956 · Severity: critical · CVSS 9.9 · Published 2026-03-10

OneUptime is an open-source monitoring and incident management platform. A low-privileged user can bypass authorization controls and tenant isolation by forging an HTTP header, allowing them to access other users' projects, read sensitive account data including password reset tokens, and fully take over victim accounts without any additional exploitation steps.

Technologies: Hackerbay Oneuptime, @oneuptime/common (npm), OneUptime. Vendors: Hackerbay, npm, OneUptime.

Quick answers

Is CVE-2026-30956 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-30956 being exploited in the wild.
How severe is CVE-2026-30956?: Critical severity, with a CVSS score of 9.9, published 10 March 2026.
Which products and versions are affected?: @oneuptime/common (npm) SEMVER:introduced=0,fixed=10.0.21; OneUptime < 10.0.21.
Is there a fix for CVE-2026-30956?: Yes. @oneuptime/common (npm): upgrade to 10.0.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-30956 attacked?: It is attacked over the network.
Am I affected by CVE-2026-30956?: Check whether you run Hackerbay Oneuptime, @oneuptime/common (npm) or OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@oneuptime/common (npm): upgrade to 10.0.21 or later
```
npm install @oneuptime/common@10.0.21
```

Technical details

The vulnerability is an authorization bypass and tenant isolation failure in OneUptime v10.0.20 and earlier. The API server trusts a client-controlled HTTP header (is-multi-tenant-query) to determine whether permission checks should be skipped. When this header is present, all permission validation layers in BasePermission are bypassed, including table-level, query-level, and select-level checks. An authenticated attacker can send this forged header to access cross-tenant data, including sensitive fields like plaintext password reset tokens stored in the User model. Combined with the password reset endpoint, this enables full account takeover. The vulnerability requires authentication but affects all multi-tenant isolation mechanisms. Patched in version 10.0.21.

Affected products

OneUptime OneUptime < 10.0.21

Identifiers

CVE-2026-30956
GHSA-r5v6-2599-9g3m

Timeline

2026-03-10: disclosed
2026-03-08: patched: Version 10.0.21 released

References

https://github.com/OneUptime/oneuptime/security/advisories/GHSA-r5v6-2599-9g3m

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.