Unauthenticated workflow execution via unguarded ManualAPI routes
Published Apr 2, 2026 · Updated Apr 2, 2026
Missing authentication in OneUptime before 10.0.42 allows remote attackers to execute workflows with attacker-controlled input. The ManualAPI registers GET and POST /workflow/manual/run/:workflowId routes without authentication and queues req.body.data as workflow return values. An attacker must obtain or guess a workflow ID; execution can run existing JavaScript steps, send notifications, alter data, or congest the worker queue.
Summary
What happened
Missing authentication in OneUptime before 10.0.42 allows remote attackers to execute workflows with attacker-controlled input. The ManualAPI registers GET and POST /workflow/manual/run/:workflowId routes without authentication and queues req.body.data as workflow return values. An attacker must obtain or guess a workflow ID; execution can run existing JavaScript steps, send notifications, alter data, or congest the worker queue.
The record
- CVE
- CVE-2026-35053
- Published
- Apr 2, 2026
- Updated
- Apr 2, 2026
- Vendor
- OneUptime
- Product
- OneUptime
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2026CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 10.0.42
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor-advisory curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo