CVE-2026-35053
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOneUptime is an open-source monitoring and observability platform. Prior to version 10.0.42, the Worker service's ManualAPI exposes workflow execution endpoints (GET /workflow/manual/run/:workflowId and POST /workflow/manual/run/:workflowId) without any authentication middleware. An attacker who can obtain or guess a workflow ID can trigger arbitrary workflow execution with attacker-controlled input data, enabling JavaScript code execution, notification abuse, and data manipulation. This issue has been patched in version 10.0.42.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Worker service's ManualAPI exposes workflow execution endpoints (GET/POST /workflow/manual/run/:workflowId) without any authentication middleware, allowing unauthenticated attackers to trigger arbitrary workflow execution with attacker-controlled input data by simply knowing or guessing a workflow ID.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.42CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OneUptime installation versionLocate the installed OneUptime version by checking package.json, a version file, or running a version command if available in the deploymentAffected if The installed version is below 10.0.42
-
Verify ManualAPI endpoint exposureAttempt a request to the /workflow/manual/run/:workflowId endpoint (GET or POST) without providing any authentication credentials or session tokenAffected if The request succeeds and returns a valid response instead of rejecting due to missing or invalid authentication
-
Confirm no authentication middleware on workflow endpointsInspect the ManualAPI route definitions in the codebase (typically in the API routes configuration) to verify whether authentication middleware is applied to the /workflow/manual/run endpointsAffected if No authentication middleware (such as auth guards, session validation, or token verification) is present on those route handlers
-
Check workflow ID accessibilityDetermine if workflow IDs can be enumerated or guessed, or if they are exposed in logs, URLs, or other outputs that an unauthenticated attacker could obtainAffected if Workflow IDs are predictable, sequentially generated, or exposed in a way that allows unauthenticated enumeration
A system is affected if it runs OneUptime version below 10.0.42 AND the ManualAPI /workflow/manual/run endpoints are accessible without authentication, allowing attackers with knowledge of a workflow ID to execute arbitrary workflows.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.42
Upgrade to version 10.0.42 or implement authentication middleware on the ManualAPI workflow execution endpoints to verify requester identity before allowing workflow execution.
10.0.42
- Back up the current OneUptime installation and database
- Stop all running OneUptime services
- Upgrade OneUptime to version 10.0.42 or later using your deployment method (e.g., Docker, npm, or Helm)
- Verify the patch was applied by checking that authentication middleware now protects /workflow/manual/run/:workflowId endpoints
- Restart the OneUptime services
- Test that the workflow execution endpoints now require valid authentication credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35053 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data