VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@oneuptime/common: vulnerability history, versions and safety

@oneuptime/common is a package in the npm ecosystem. Vulert records 11 vulnerabilities for it across 120 releases, from Nov 2025 to 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
11 vulnerabilities recorded C6 H3 M2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
11 in the last 12 months

Most recent disclosure 10 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @oneuptime/common vulnerabilities

Vulert verdict on @oneuptime/common 14.0.85 i

Updated on 23 Oct 2026

Careful: 14.0.85 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 14.0.85 — affected i
  • Vulnerabilities on record 11 over 1 year · 11 in the last year i
  • Latest disclosure 10 Mar 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 1 i
  • Stars 7,745 i
  • Last release this month i
  • Licence Apache-2.0 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/common, 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
14.0.85 22 Oct 2026 H1 Apache-2.0 No Details →
14.0.84 22 Oct 2026 H1 Apache-2.0 No Details →
14.0.83 21 Oct 2026 H1 Apache-2.0 No Details →
14.0.82 21 Oct 2026 H1 Apache-2.0 No Details →
14.0.81 21 Oct 2026 H1 Apache-2.0 No Details →
14.0.80 21 Oct 2026 H1 Apache-2.0 No Details →
14.0.79 20 Oct 2026 H1 Apache-2.0 No Details →
14.0.78 20 Oct 2026 H1 Apache-2.0 No Details →
14.0.77 20 Oct 2026 H1 Apache-2.0 No Details →
14.0.76 19 Oct 2026 H1 Apache-2.0 No Details →
14.0.75 19 Oct 2026 H1 Apache-2.0 No Details →
14.0.74 19 Oct 2026 H1 Apache-2.0 No Details →
14.0.73 19 Oct 2026 H1 Apache-2.0 No Details →
14.0.72 18 Oct 2026 H1 Apache-2.0 No Details →
14.0.71 18 Oct 2026 H1 Apache-2.0 No Details →
14.0.70 18 Oct 2026 H1 Apache-2.0 No Details →
14.0.69 18 Oct 2026 H1 Apache-2.0 No Details →
14.0.68 18 Oct 2026 H1 Apache-2.0 No Details →
14.0.67 17 Oct 2026 H1 Apache-2.0 No Details →
14.0.66 17 Oct 2026 H1 Apache-2.0 No Details →
14.0.65 17 Oct 2026 H1 Apache-2.0 No Details →
14.0.64 16 Oct 2026 H1 Apache-2.0 No Details →
14.0.63 16 Oct 2026 H1 Apache-2.0 No Details →
14.0.62 16 Oct 2026 H1 Apache-2.0 No Details →
14.0.61 15 Oct 2026 H1 Apache-2.0 No Details →
14.0.60 15 Oct 2026 H1 Apache-2.0 No Details →
14.0.59 15 Oct 2026 H1 Apache-2.0 No Details →
14.0.58 15 Oct 2026 H1 Apache-2.0 No Details →
14.0.57 14 Oct 2026 H1 Apache-2.0 No Details →
14.0.56 14 Oct 2026 H1 Apache-2.0 No Details →
14.0.55 14 Oct 2026 H1 Apache-2.0 No Details →
14.0.54 14 Oct 2026 H1 Apache-2.0 No Details →
14.0.53 14 Oct 2026 H1 Apache-2.0 No Details →
14.0.52 13 Oct 2026 H1 Apache-2.0 No Details →
14.0.51 13 Oct 2026 H1 Apache-2.0 No Details →
14.0.50 13 Oct 2026 H1 Apache-2.0 No Details →
14.0.49 13 Oct 2026 H1 Apache-2.0 No Details →
14.0.48 13 Oct 2026 H1 Apache-2.0 No Details →
14.0.47 12 Oct 2026 H1 Apache-2.0 No Details →
14.0.46 12 Oct 2026 H1 Apache-2.0 No Details →
14.0.45 12 Oct 2026 H1 Apache-2.0 No Details →
14.0.44 12 Oct 2026 H1 Apache-2.0 No Details →
14.0.43 12 Oct 2026 H1 Apache-2.0 No Details →
14.0.42 12 Oct 2026 H1 Apache-2.0 No Details →
14.0.41 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.40 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.39 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.38 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.37 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.36 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.35 11 Oct 2026 H1 Apache-2.0 No Details →
14.0.34 10 Oct 2026 H1 Apache-2.0 No Details →
14.0.33 10 Oct 2026 H1 Apache-2.0 No Details →
14.0.32 10 Oct 2026 H1 Apache-2.0 No Details →
14.0.31 10 Oct 2026 H1 Apache-2.0 No Details →
14.0.30 10 Oct 2026 H1 Apache-2.0 No Details →
14.0.29 10 Oct 2026 H1 Apache-2.0 No Details →
14.0.28 09 Oct 2026 H1 Apache-2.0 No Details →
14.0.27 09 Oct 2026 H1 Apache-2.0 No Details →
14.0.26 09 Oct 2026 H1 Apache-2.0 No Details →
14.0.25 09 Oct 2026 H1 Apache-2.0 No Details →
14.0.24 09 Oct 2026 H1 Apache-2.0 No Details →
14.0.23 08 Oct 2026 H1 Apache-2.0 No Details →
14.0.22 08 Oct 2026 H1 Apache-2.0 No Details →
14.0.21 08 Oct 2026 H1 Apache-2.0 No Details →
14.0.20 08 Oct 2026 H1 Apache-2.0 No Details →
14.0.19 08 Oct 2026 H1 Apache-2.0 No Details →
14.0.18 07 Oct 2026 H1 Apache-2.0 No Details →
14.0.17 07 Oct 2026 H1 Apache-2.0 No Details →
14.0.16 07 Oct 2026 H1 Apache-2.0 No Details →
14.0.15 07 Oct 2026 H1 Apache-2.0 No Details →
14.0.14 04 Oct 2026 H1 Apache-2.0 No Details →
14.0.13 03 Oct 2026 H1 Apache-2.0 No Details →
14.0.12 02 Oct 2026 H1 Apache-2.0 No Details →
14.0.11 01 Oct 2026 H1 Apache-2.0 No Details →
14.0.10 30 Sep 2026 H1 Apache-2.0 No Details →
14.0.9 29 Sep 2026 H1 Apache-2.0 No Details →
14.0.8 28 Sep 2026 H1 Apache-2.0 No Details →
14.0.7 27 Sep 2026 H1 Apache-2.0 No Details →
14.0.6 26 Sep 2026 H1 Apache-2.0 No Details →
14.0.5 26 Sep 2026 H1 Apache-2.0 No Details →
14.0.3 25 Sep 2026 H1 Apache-2.0 No Details →
14.0.2 24 Sep 2026 H1 Apache-2.0 No Details →
14.0.1 22 Sep 2026 H1 Apache-2.0 No Details →
14.0.0 21 Sep 2026 H1 Apache-2.0 No Details →
13.0.8 19 Sep 2026 H1 Apache-2.0 No Details →
13.0.7 18 Sep 2026 H1 Apache-2.0 No Details →
13.0.6 16 Sep 2026 H1 Apache-2.0 No Details →
13.0.5 15 Sep 2026 H1 Apache-2.0 No Details →
13.0.4 13 Sep 2026 H1 Apache-2.0 No Details →
13.0.3 12 Sep 2026 H1 Apache-2.0 No Details →
13.0.1 11 Sep 2026 H1 Apache-2.0 No Details →
13.0.0 07 Sep 2026 H1 Apache-2.0 No Details →
12.0.34 06 Sep 2026 H1 Apache-2.0 No Details →
12.0.33 04 Sep 2026 H1 Apache-2.0 No Details →
12.0.32 03 Sep 2026 H1 Apache-2.0 No Details →
12.0.31 02 Sep 2026 H1 Apache-2.0 No Details →
12.0.30 01 Sep 2026 H1 Apache-2.0 No Details →
12.0.29 31 Aug 2026 H1 Apache-2.0 No Details →
12.0.28 29 Aug 2026 H1 Apache-2.0 No Details →
12.0.27 29 Aug 2026 H1 — No Details →
12.0.26 29 Aug 2026 H1 — No Details →
12.0.25 27 Aug 2026 H1 — No Details →
12.0.24 27 Aug 2026 H1 — No Details →
12.0.23 25 Aug 2026 H1 — No Details →
12.0.22 25 Aug 2026 H1 — No Details →
12.0.21 25 Aug 2026 H1 — No Details →
12.0.20 24 Aug 2026 H1 — No Details →
12.0.19 24 Aug 2026 H1 — No Details →
12.0.18 23 Aug 2026 H1 — No Details →
12.0.17 22 Aug 2026 H1 — No Details →
12.0.16 22 Aug 2026 H1 — No Details →
12.0.15 22 Aug 2026 H1 — No Details →
12.0.14 20 Aug 2026 H1 — No Details →
12.0.13 19 Aug 2026 H1 — No Details →
12.0.12 18 Aug 2026 H1 — No Details →
12.0.11 17 Aug 2026 H1 — No Details →
12.0.10 16 Aug 2026 H1 — No Details →
12.0.9 15 Aug 2026 H1 — No Details →
12.0.8 13 Aug 2026 H1 — No Details →

The newest 120 of 1,226 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for @oneuptime/common

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-27574: OneUptime @oneuptime/common Package RCE via Node.js vm Sandbox Escape 9.9 critical 10.0.0 24 Feb 2026
CVE-2026-27728: OS Command Injection in @oneuptime/common NetworkPathMonitor 9.9 critical 10.0.7 25 Feb 2026
Critical Remote Code Execution Vulnerability in @oneuptime/common Package 9.9 critical 10.0.20 07 Mar 2026
Critical Remote Code Execution Vulnerability in @oneuptime/common Package 9.9 critical 10.0.18 07 Mar 2026
CVE-2026-30957: OneUptime @oneuptime/common Package Remote Code Execution Vulnerability 9.9 critical 10.0.21 10 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/common

Is @oneuptime/common safe to use?

Vulert records 11 vulnerabilities for @oneuptime/common in npm: 6 critical, 3 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is @oneuptime/common's Vulert package health score?

Vulert scores @oneuptime/common 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of @oneuptime/common affected?

Yes. 14.0.85, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does @oneuptime/common have?

11 vulnerabilities are recorded for @oneuptime/common in the npm ecosystem: 6 critical, 3 high, 2 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/common vulnerabilities disclosed?

11 vulnerabilities were recorded for @oneuptime/common in the last 12 months, and the oldest entry in this database dates to 25 Nov 2025. 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/common 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/common for upcoming vulnerabilities?

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