VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@backstage/plugin-scaffolder-backend-module-bitbucket-cloud: vulnerability history, versions and safety

@backstage/plugin-scaffolder-backend-module-bitbucket-cloud is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 113 releases, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @backstage/plugin-scaffolder-backend-module-bitbucket-cloud vulnerabilities

Vulert verdict on @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 0.3.12 i

Updated on 23 Oct 2026

Good news: 0.3.12, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.3.12 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 07 Oct 2026 i
  • Highest CVSS 8.5 i
  • With no published fix 0 i
  • Depended on by 87 packages i
  • Stars 34,659 i
  • OpenSSF scorecard 6/10 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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud, 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
0.3.12 20 Oct 2026 none Apache-2.0 — Details →
0.3.12-next.1 29 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260928023907 28 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260927023342 27 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260926022852 26 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260925022940 25 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260924023050 24 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260923023054 23 Sep 2026 H1 Apache-2.0 Yes Details →
0.3.12-next.0 22 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260922023058 22 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260921023416 21 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260920023043 20 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260919022921 19 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260918023200 18 Sep 2026 H1 Apache-2.0 Yes Details →
0.3.11 15 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260909022715 09 Sep 2026 H1 Apache-2.0 Yes Details →
0.3.11-next.2 08 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260904022803 04 Sep 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260902024315 02 Sep 2026 H1 Apache-2.0 Yes Details →
0.3.11-next.1 01 Sep 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260829022506 29 Aug 2026 H1 Apache-2.0 Yes Details →
0.3.10 28 Aug 2026 none Apache-2.0 — Details →
0.0.0-nightly-20260828045505 28 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260827035829 27 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260826023806 26 Aug 2026 H1 Apache-2.0 Yes Details →
0.3.10-next.0 25 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260825023435 25 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260824023732 24 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260823023807 23 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260822023239 22 Aug 2026 H1 Apache-2.0 Yes Details →
0.3.9 18 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260818023149 18 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260817023522 17 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260816023538 16 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260815023121 15 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260814030239 14 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260813030414 13 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260812030228 12 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260811025108 11 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260810025551 10 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260809025047 09 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260808024620 08 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260807031145 07 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260806031410 06 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260805031525 05 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260804031620 04 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260803031511 03 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260802031400 02 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260801031325 01 Aug 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260731031617 31 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260730031533 30 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260729031221 29 Jul 2026 H1 Apache-2.0 Yes Details →
0.3.9-next.1 28 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260728031313 28 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260727031641 27 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260726031454 26 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260725031401 25 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260724031548 24 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260723031410 23 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260722031354 22 Jul 2026 H1 Apache-2.0 Yes Details →
0.3.9-next.0 21 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260721031542 21 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260720031650 20 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260719031424 19 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260718031341 18 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260717031454 17 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260716031633 16 Jul 2026 H1 Apache-2.0 Yes Details →
0.3.8 14 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260714031447 14 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260713031604 13 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260712031654 12 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260711031351 11 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260710031816 10 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260709031947 09 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260707031921 07 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260706032134 06 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260705031809 05 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260704031505 04 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260703031634 03 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260702032027 02 Jul 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260630032100 30 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260629032440 29 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260628032241 28 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260627032140 27 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260626032136 26 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260625032153 25 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260624032139 24 Jun 2026 H1 Apache-2.0 Yes Details →
0.3.8-next.0 23 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260623032249 23 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260622032447 22 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260621032345 21 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260620032105 20 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260619032606 19 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260618032436 18 Jun 2026 H1 Apache-2.0 Yes Details →
0.3.7 16 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260616032439 16 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260615032517 15 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260614032343 14 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260613032133 13 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260612032440 12 Jun 2026 H1 Apache-2.0 Yes Details →
0.0.0-nightly-20260611032059 11 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260610032156 10 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260609032118 09 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260608032505 08 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260607032244 07 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260606031950 06 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260605032312 05 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260604032348 04 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260603032450 03 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260602032639 02 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260601032430 01 Jun 2026 H1 — Yes Details →
0.0.0-nightly-20260531032321 31 May 2026 H1 — Yes Details →
0.0.0-nightly-20260530032139 30 May 2026 H1 — Yes Details →
0.0.0-nightly-20260529032432 29 May 2026 H1 — Yes Details →
0.0.0-nightly-20260528032551 28 May 2026 H1 — Yes Details →
0.0.0-nightly-20260527032423 27 May 2026 H1 — Yes Details →
0.3.7-next.0 26 May 2026 H1 — Yes Details →
0.0.0-nightly-20260526032421 26 May 2026 H1 — Yes Details →
0.3.6 19 May 2026 H1 — Yes Details →
0.0.0-nightly-20260519032312 19 May 2026 H1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for @backstage/plugin-scaffolder-backend-module-bitbucket-cloud

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-106486: Improper Filesystem Validation in Backstage Bitbucket Scaffolder Actions 8.5 high 0.3.10 07 Oct 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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud

Is @backstage/plugin-scaffolder-backend-module-bitbucket-cloud safe to use?

Vulert records 1 vulnerabilities for @backstage/plugin-scaffolder-backend-module-bitbucket-cloud in npm: 0 critical, 1 high, 0 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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud's Vulert package health score?

Vulert scores @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 84/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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud affected?

No. 0.3.12, 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.

How many vulnerabilities does @backstage/plugin-scaffolder-backend-module-bitbucket-cloud have?

1 vulnerability is recorded for @backstage/plugin-scaffolder-backend-module-bitbucket-cloud in the npm ecosystem: 0 critical, 1 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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud vulnerabilities disclosed?

1 vulnerability was recorded for @backstage/plugin-scaffolder-backend-module-bitbucket-cloud in the last 12 months, and the oldest entry in this database dates to 07 Oct 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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud 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 @backstage/plugin-scaffolder-backend-module-bitbucket-cloud for upcoming vulnerabilities?

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