Vulnerability · Published Mar 9, 2026 · Assigned by GitHub_M

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

High 8.6

In plain English

A high-severity insufficient verification of data authenticity in oneuptime from OneUptime. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 14% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.6High

Exploit odds (30 days)0.2%top 86.0% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	@oneuptime/common	10.0.19	GHSA-656w-6f6c-m9r6

Affected products (as reported)

Vendor	Product	Versions
OneUptime	oneuptime	< 10.0.19

Weakness: CWE-345, CWE-639, CWE-862 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

References

https://github.com/OneUptime/oneuptime/security/advisories/GHSA-656w-6f6c-m9r6 x_refsource_CONFIRM