VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@nextcloud/upload: vulnerability history, versions and safety

@nextcloud/upload is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @nextcloud/upload vulnerabilities

Vulert verdict on @nextcloud/upload 1.12.0 i

Updated on 23 Oct 2026

Good news: 1.12.0, the version you would install today, has no known vulnerabilities.

Package health score 80/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 1.12.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.12.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.12.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 1 month ago i
  • Licence AGPL-3.0-or-later 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 @nextcloud/upload, 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
1.12.0 02 Sep 2026 none AGPL-3.0-or-later — Details →
1.11.1 29 Jan 2026 none AGPL-3.0-or-later — Details →
1.11.0 11 Sep 2025 none AGPL-3.0-or-later — Details →
2.0.0-rc.0 01 Jul 2025 none AGPL-3.0-or-later — Details →
1.10.0 05 May 2025 none AGPL-3.0-or-later — Details →
1.9.1 20 Mar 2025 none AGPL-3.0-or-later — Details →
1.9.0 04 Mar 2025 none AGPL-3.0-or-later — Details →
1.8.0 21 Jan 2025 none AGPL-3.0-or-later — Details →
1.7.1 10 Dec 2024 none AGPL-3.0-or-later — Details →
1.7.0 13 Nov 2024 none AGPL-3.0-or-later — Details →
1.6.2 13 Nov 2024 none AGPL-3.0-or-later — Details →
1.6.1 25 Sep 2024 none AGPL-3.0-or-later — Details →
1.6.0 05 Sep 2024 none AGPL-3.0-or-later — Details →
1.5.0 20 Aug 2024 none AGPL-3.0-or-later — Details →
1.4.3 07 Aug 2024 none AGPL-3.0-or-later — Details →
1.4.2 12 Jul 2024 none AGPL-3.0-or-later — Details →
1.4.1 24 Jun 2024 none AGPL-3.0-or-later — Details →
1.4.0 21 Jun 2024 none AGPL-3.0-or-later — Details →
1.3.0 07 Jun 2024 none AGPL-3.0-or-later — Details →
1.2.0 23 May 2024 none AGPL-3.0-or-later — Details →
1.1.1 15 Apr 2024 none AGPL-3.0-or-later — Details →
1.1.0 02 Apr 2024 none AGPL-3.0-or-later — Details →
1.0.5 14 Feb 2024 none AGPL-3.0-or-later — Details →
1.0.4 15 Dec 2023 none AGPL-3.0-or-later — Details →
1.0.3 07 Dec 2023 none AGPL-3.0-or-later — Details →
1.0.2 29 Nov 2023 none AGPL-3.0-or-later — Details →
1.0.1 17 Nov 2023 none AGPL-3.0-or-later — Details →
1.0.0 08 Nov 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.19 26 Oct 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.18 12 Oct 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.17 01 Sep 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.16 01 Sep 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.15 31 Aug 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.14 29 Aug 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.13 24 Aug 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.12 18 Aug 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.11 17 Aug 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.10 07 Jul 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.9 24 May 2023 none AGPL-3.0-or-later — Details →
1.0.0-beta.8 17 Sep 2022 none AGPL-3.0-or-later — Details →
1.0.0-beta.7 16 Sep 2022 none AGPL-3.0-or-later — Details →
1.0.0-beta.6 14 Sep 2022 none AGPL-3.0-or-later — Details →
1.0.0-beta.5 08 Sep 2022 none AGPL-3.0-or-later — Details →
1.0.0-beta.4 01 Sep 2022 none AGPL-3.0-or-later — Details →
1.0.0-beta.3 31 Aug 2022 none AGPL-3.0-or-later — Details →
1.0.0-beta.2 31 Aug 2022 none AGPL-3.0-or-later — Details →
1.1.0-beta.1 06 Jul 2022 none AGPL-3.0-or-later — Details →
1.1.0-beta.0 06 Jul 2022 none AGPL-3.0-or-later — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @nextcloud/upload

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 @nextcloud/upload

Is @nextcloud/upload safe to use?

Vulert has no vulnerabilities on record for @nextcloud/upload in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @nextcloud/upload's Vulert package health score?

Vulert scores @nextcloud/upload 80/100, which reads as in good shape. 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 @nextcloud/upload affected?

No. 1.12.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @nextcloud/upload should I use?

1.12.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @nextcloud/upload have?

0 vulnerabilities are recorded for @nextcloud/upload in the npm ecosystem: 0 critical, 0 high, 0 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 @nextcloud/upload vulnerabilities disclosed?

0 vulnerabilities were recorded for @nextcloud/upload in the last 12 months. 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 @nextcloud/upload 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 @nextcloud/upload for upcoming vulnerabilities?

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