CVE-2026-35053
The vulnerability allows unauthenticated users to trigger any workflow in OneUptime’s Worker service. By guessing a workflow ID, an attacker can run arbitrary code, send unwanted notifications, or alter data. The flaw was fixed in version 10.0.42.
An official fix is available, so this entry is kept for 30 days and then removed automatically.
Who is affected
OneUptime open‑source monitoring platform, versions prior to 10.0.42, especially the Worker service’s ManualAPI endpoints. Administrators or users who can guess workflow IDs are at risk.
Real-world impact
An attacker who can guess a workflow ID can execute arbitrary JavaScript, abuse notification channels, and modify or delete data stored by OneUptime.
Why this severity
The CVSS score of 9.2 reflects that the flaw is remote, requires no authentication, and can compromise confidentiality, integrity, and availability of the system, giving attackers full control over workflow execution.
What to do about it
- 01Upgrade OneUptime to version 10.0.42 or later.
- 02Restart the Worker service to apply the patch.
NVD-referenced vendor advisory
Timeline
- Apr 2, 2026 · Apr 2, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 24, 2026 · 11d agoAdvisory updatedThe NVD record was last revised.
- Jul 26, 2026 · 10d agoOfficial fix availableA vendor patch or mitigation now exists — see the remediation steps above.
How it’s attacked
References & advisories
- github.com/OneUptime/oneuptime/release…productrelease notes
- github.com/OneUptime/oneuptime/securit…exploitvendor advisory