# OneUptime has broken access control in GitHub App installation flow that allows unauthorized project binding

Advisory record · `GHSA-656w-6f6c-m9r6`

- **Identifiers:** `GHSA-656w-6f6c-m9r6` · `CVE-2026-30920`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html) · [CWE-639](https://cwe.mitre.org/data/definitions/639.html) · [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) · [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md)
- **Published:** 9 Mar 2026
- **Updated:** 10 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Mar 2026, 17:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `@oneuptime/common` (npm): affected `<10.0.19`; fixed in `10.0.19`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.6 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 13th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 9 Mar 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-656w-6f6c-m9r6](https://github.com/advisories/GHSA-656w-6f6c-m9r6)
- [OSV: GHSA-656w-6f6c-m9r6](https://osv.dev/vulnerability/GHSA-656w-6f6c-m9r6)
- <https://github.com/OneUptime/oneuptime/security/advisories/GHSA-656w-6f6c-m9r6>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-30920>
- <https://github.com/OneUptime/oneuptime>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/API/GitHubAPI.ts#L127-L165>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/API/GitHubAPI.ts#L179-L258>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/API/GitHubAPI.ts#L260-L356>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/API/GitHubAPI.ts#L34-L112>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/API/GitHubAPI.ts#L73-L79>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/Middleware/UserAuthorization.ts#L205-L211>
- <https://github.com/OneUptime/oneuptime/blob/master/Common/Server/Utils/CodeRepository/GitHub/GitHub.ts#L347-L425>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-656w-6f6c-m9r6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-656w-6f6c-m9r6/>. Everything for agents: <https://agentprime.io/llms.txt>.