VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

oneuptime: vulnerability history, versions and safety

oneuptime is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 66 releases, first recorded in Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C1 H3 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
5 in the last 12 months

Most recent disclosure 18 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all oneuptime vulnerabilities

Vulert verdict on oneuptime 4.0.69 i

Updated on 23 Oct 2026

Action needed: 4.0.69 has 5 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 42/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 4.0.69 — affected i
  • Vulnerabilities on record 5 over 1 year · 5 in the last year i
  • Latest disclosure 18 Mar 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Stars 1 i
  • Last release 52 months ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for oneuptime, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.0.69 20 Jun 2022 C1 H3 M1 ISC Yes Details →
4.0.68 02 May 2022 C1 H3 M1 ISC Yes Details →
4.0.67 09 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.66 09 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.65 09 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.64 09 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.63 08 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.62 07 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.61 07 Apr 2022 C1 H3 M1 ISC Yes Details →
4.0.60 31 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.59 31 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.58 31 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.57 31 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.56 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.55 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.54 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.53 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.52 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.51 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.50 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.49 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.48 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.47 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.46 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.45 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.44 29 Mar 2022 C1 H3 M1 ISC Yes Details →
4.0.43 25 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.42 25 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.41 25 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.40 24 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.39 24 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.38 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.37 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.36 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.35 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.34 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.33 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.32 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.31 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.30 23 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.29 18 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.28 17 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.27 17 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.26 17 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.25 17 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.24 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.23 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.22 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.21 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.20 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.19 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.18 12 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.17 11 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.16 11 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.15 11 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.14 11 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.13 11 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.12 08 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.11 08 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.10 07 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.9 07 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.8 07 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.7 07 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.6 06 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.5 06 Feb 2022 C1 H3 M1 ISC Yes Details →
4.0.3 05 Feb 2022 C1 H3 M1 ISC Yes Details →

All 66 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for oneuptime

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-32306: OneUptime SQL Injection Vulnerability in ClickHouse Aggregation API 9.9 critical 10.0.23 13 Mar 2026
CVE-2026-33143: OneUptime WhatsApp Webhook Missing Signature Verification Vulnerability 8.7 high 10.0.34 18 Mar 2026
CVE-2026-33142: OneUptime SQL Injection Vulnerability via Unvalidated Column Identifiers 8.1 high 10.0.34 18 Mar 2026
CVE-2026-32308: OneUptime Stored XSS via Mermaid Diagram Rendering 7.6 high 10.0.23 13 Mar 2026
CVE-2026-32598: OneUptime Password Reset Token Exposed in Logs 6.9 medium 10.0.23 13 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About oneuptime

Is oneuptime safe to use?

Vulert records 5 vulnerabilities for oneuptime in npm: 1 critical, 3 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is oneuptime's Vulert package health score?

Vulert scores oneuptime 42/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of oneuptime affected?

Yes. 4.0.69, the version you would install today, has 5 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does oneuptime have?

5 vulnerabilities are recorded for oneuptime in the npm ecosystem: 1 critical, 3 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new oneuptime vulnerabilities disclosed?

5 vulnerabilities were recorded for oneuptime in the last 12 months, and the oldest entry in this database dates to 13 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of oneuptime are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor oneuptime for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the oneuptime version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.