# CVE-2026-30920: OneUptime has broken access control in GitHub App installation flow that allows unauthorized project binding

> Attackers can bind arbitrary GitHub App installations to other projects and enumerate repositories due to missing authorization checks in the callback flow.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-656w-6f6c-m9r6

## What is CVE-2026-30920?

CVE-2026-30920 is a high-severity missing authorization vulnerability in oneuptime, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OneUptime is a solution for monitoring and managing online services. Prior to 10.0.19, OneUptime's GitHub App callback trusts attacker-controlled state and installation_id values and updates Project.gitHubAppInstallationId with isRoot: true without validating that the caller is authorized for the target project. This allows an attacker to overwrite another project's GitHub App installation binding. Related GitHub endpoints also lack effective authorization, so a valid installation ID can be used to enumerate repositories and create CodeRepository records in an arbitrary project. This vulnerability is fixed in 10.0.19.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-30920?

2 open source packages ship an affected version, including @oneuptime/common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@oneuptime/common` | npm | All versions | 10.0.19 |
| `@oneuptime/common` | npm | All versions | 10.0.19 |

Products: Hackerbay Oneuptime.

## How do I fix CVE-2026-30920?

Upgrade @oneuptime/common to 10.0.19 or later.

## Is CVE-2026-30920 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30920 exists.

## Other vulnerabilities in oneuptime

- [CVE-2026-33396](https://insights.sbomify.com/CVE-2026-33396/): Code injection in oneuptime (critical 10.0)
- [CVE-2026-32306](https://insights.sbomify.com/CVE-2026-32306/): OneUptime ClickHouse SQL Injection via Aggregate Query Parameters (critical 10.0)
- [CVE-2026-30956](https://insights.sbomify.com/CVE-2026-30956/): OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header (critical 10.0)
- [CVE-2026-30957](https://insights.sbomify.com/CVE-2026-30957/): OneUptime Synthetic Monitor RCE via exposed Playwright browser object (critical 10.0)
- [CVE-2026-30887](https://insights.sbomify.com/CVE-2026-30887/): OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30920 and fix it if it is affected.

What it is: CVE-2026-30920 is a high-severity missing authorization vulnerability in oneuptime, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30920 exists.

Affected packages and fixed versions:
- @oneuptime/common (npm): affected all versions; fixed in 10.0.19
- @oneuptime/common (npm): affected all versions; fixed in 10.0.19

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30920/ (Markdown: https://insights.sbomify.com/CVE-2026-30920/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30920
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30920
- OSV: https://osv.dev/vulnerability/CVE-2026-30920

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30920/
Summaries are generated and may contain mistakes; the official description above is the record.