Multiple vulnerabilities have been discovered in Oneuptime, an open-source monitoring and observability platform. These vulnerabilities could lead to financial abuse via phone number purchase, service disruption, and authentication bypass. Version 10.0.42 addresses these issues.
One vulnerability has a CVSS score of 8.1, indicating a high severity risk.
What is Oneuptime?
CVE-2026-34759: Unauthenticated notification API endpoints
No CVSS score assigned.
EPSS score not available.
Unauthenticated API endpoints in Oneuptime's notification service allow attackers to perform actions without proper authorization. An attacker could exploit this, combined with a project ID leak, to purchase phone numbers on the victim's Twilio account and delete existing alerting numbers, leading to financial abuse and service disruption.
How to fix CVE-2026-34759 in Oneuptime
Patch immediately- 1.Update Oneuptime to version 10.0.42 or later.
npm update oneuptimeWorkaround: No known workaround.
NextGuard automatically flags CVE-2026-34759 if Oneuptime appears in any of your monitored projects — no manual lookup required.
CVE-2026-34840: Multi-Assertion Identity Injection in SSO
High severity due to potential for authentication bypass.
EPSS score not available.
Oneuptime's SAML SSO implementation decouples signature verification and identity extraction. An attacker can prepend an unsigned assertion containing an arbitrary identity before a legitimately signed assertion, bypassing authentication and gaining unauthorized access.
How to fix CVE-2026-34840 in Oneuptime
Patch immediately- 1.Update Oneuptime to version 10.0.42 or later.
npm update oneuptimeWorkaround: No known workaround.
NextGuard automatically flags CVE-2026-34840 if Oneuptime appears in any of your monitored projects — no manual lookup required.
CVE-2026-35053: Unauthenticated Workflow Execution
No CVSS score assigned.
EPSS score not available.
The Worker service's ManualAPI in Oneuptime exposes workflow execution endpoints without authentication. An attacker who can obtain or guess a workflow ID can trigger arbitrary workflow execution with attacker-controlled input data, leading to JavaScript code execution, notification abuse, and data manipulation.
How to fix CVE-2026-35053 in Oneuptime
Patch immediately- 1.Update Oneuptime to version 10.0.42 or later.
npm update oneuptimeWorkaround: No known workaround.
NextGuard automatically flags CVE-2026-35053 if Oneuptime appears in any of your monitored projects — no manual lookup required.
Stay ahead of nodejs vulnerabilities
Proactively detect and respond to vulnerabilities affecting your nodejs applications. monitor your nodejs dependencies.
Compare PlansFrequently asked questions
Multiple vulnerabilities were discovered in Oneuptime, and users are advised to update to version 10.0.42 immediately. Stay informed about the latest security threats and see all nodejs vulnerabilities. Regularly updating your dependencies is crucial for maintaining a secure environment.
Related topics