Vulnerability Database · npm · Package report

@cloudflare/workers-oauth-provider: vulnerability history, versions and safety

@cloudflare/workers-oauth-provider is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 33 releases, first recorded in May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
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.

Vulert verdict on @cloudflare/workers-oauth-provider 1.2.4 i

Updated on 23 Oct 2026

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

Package health score 89/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 1.2.4 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 01 May 2025 i
  • Highest CVSS 6.0 i
  • With no published fix 0 i
  • Stars 1,887 i
  • Last release this month i
  • Licence MIT 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 @cloudflare/workers-oauth-provider, 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.2.4 22 Oct 2026 none MIT — Details →
1.2.3 07 Oct 2026 none MIT — Details →
1.2.2 06 Oct 2026 none MIT — Details →
1.2.1 28 Sep 2026 none MIT — Details →
1.2.0 28 Sep 2026 none MIT — Details →
1.1.0 24 Sep 2026 none MIT — Details →
1.0.0 24 Sep 2026 none MIT — Details →
0.10.4 23 Sep 2026 none MIT — Details →
0.10.3 10 Aug 2026 none MIT — Details →
0.10.2 07 Aug 2026 none MIT — Details →
0.10.1 05 Aug 2026 none MIT — Details →
0.10.0 04 Aug 2026 none MIT — Details →
0.9.1 04 Aug 2026 none MIT — Details →
0.9.0 04 Aug 2026 none MIT — Details →
0.8.3 29 Jul 2026 none MIT — Details →
0.8.2 16 Jul 2026 none MIT — Details →
0.8.1 19 Jun 2026 none MIT — Details →
0.8.0 12 Jun 2026 none MIT — Details →
0.7.2 04 Jun 2026 none MIT — Details →
0.7.1 03 Jun 2026 none MIT — Details →
0.7.0 21 May 2026 none MIT — Details →
0.6.0 13 May 2026 none MIT — Details →
0.5.0 05 May 2026 none MIT — Details →
0.4.0 31 Mar 2026 none MIT — Details →
0.3.3 31 Mar 2026 none MIT — Details →
0.3.2 29 Mar 2026 none MIT — Details →
0.3.1 25 Mar 2026 none MIT — Details →
0.3.0 04 Mar 2026 none MIT — Details →
0.2.4 26 Feb 2026 none MIT — Details →
0.2.3 11 Feb 2026 none MIT — Details →
0.2.2 20 Dec 2025 none MIT — Details →
0.0.0-be89144 07 Nov 2025 M4 MIT Yes Details →
0.1.0 07 Nov 2025 none MIT — Details →
0.0.0-f2b1372 06 Nov 2025 M4 MIT Yes Details →
0.0.0-818a557 06 Nov 2025 M4 MIT Yes Details →
0.0.0-f8eaa3e 30 Oct 2025 M4 MIT Yes Details →
0.0.13 30 Oct 2025 none MIT — Details →
0.0.0-0982a1c 30 Oct 2025 M4 MIT Yes Details →
0.0.0-50a8d92 20 Oct 2025 M4 MIT Yes Details →
0.0.12 20 Oct 2025 none MIT — Details →
0.0.0-5a59d78 20 Oct 2025 M4 MIT Yes Details →
0.0.0-b7784c7 23 Sep 2025 M4 MIT Yes Details →
0.0.11 23 Sep 2025 none MIT — Details →
0.0.0-32560d1 23 Sep 2025 M4 MIT Yes Details →
0.0.0-78be0eb 16 Sep 2025 M4 MIT Yes Details →
0.0.10 16 Sep 2025 none MIT — Details →
0.0.0-1804446 16 Sep 2025 M4 MIT Yes Details →
0.0.0-5651a05 16 Sep 2025 M4 MIT Yes Details →
0.0.9 16 Sep 2025 none MIT — Details →
0.0.0-373bacf 16 Sep 2025 M4 MIT Yes Details →
0.0.0-d18b865 16 Sep 2025 M4 MIT Yes Details →
0.0.8 15 Sep 2025 none MIT — Details →
0.0.0-aa007fc 15 Sep 2025 M4 MIT Yes Details →
0.0.0-9d4b595 15 Sep 2025 M4 MIT Yes Details →
0.0.0-75d3fe2 12 Sep 2025 M4 MIT Yes Details →
0.0.0-68e3f97 11 Sep 2025 M4 MIT Yes Details →
0.0.0-81c04c7 11 Sep 2025 M4 MIT Yes Details →
0.0.7 11 Sep 2025 none MIT — Details →
0.0.0-0b064bf 11 Sep 2025 M4 MIT Yes Details →
0.0.0-9587b58 11 Sep 2025 M4 MIT Yes Details →
0.0.0-a204c64 11 Sep 2025 M4 MIT Yes Details →
0.0.0-239e753 13 Aug 2025 M4 MIT Yes Details →
0.0.0-9cd9ab4 11 Aug 2025 M4 MIT Yes Details →
0.0.0-4d02346 08 Aug 2025 M4 MIT Yes Details →
0.0.6 07 Aug 2025 none MIT — Details →
0.0.0-6ab489d 07 Aug 2025 M4 MIT Yes Details →
0.0.0-89df9a6 07 Aug 2025 M4 MIT Yes Details →
0.0.5 30 Apr 2025 none MIT — Details →
0.0.4 28 Apr 2025 M4 MIT Yes Details →
0.0.4-1 28 Apr 2025 M4 MIT Yes Details →
0.0.4-0 24 Apr 2025 M4 MIT Yes Details →
0.0.3 10 Apr 2025 M4 MIT Yes Details →
0.0.2 20 Mar 2025 M4 MIT Yes Details →
0.0.1 16 Mar 2025 M4 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 4

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

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 @cloudflare/workers-oauth-provider

Is @cloudflare/workers-oauth-provider safe to use?

Vulert records 4 vulnerabilities for @cloudflare/workers-oauth-provider in npm: 0 critical, 0 high, 4 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 @cloudflare/workers-oauth-provider's Vulert package health score?

Vulert scores @cloudflare/workers-oauth-provider 89/100, which reads as healthy. 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 @cloudflare/workers-oauth-provider affected?

No. 1.2.4, 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 @cloudflare/workers-oauth-provider have?

4 vulnerabilities are recorded for @cloudflare/workers-oauth-provider in the npm ecosystem: 0 critical, 0 high, 4 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 @cloudflare/workers-oauth-provider vulnerabilities disclosed?

0 vulnerabilities were recorded for @cloudflare/workers-oauth-provider in the last 12 months, and the oldest entry in this database dates to 01 May 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 @cloudflare/workers-oauth-provider 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 @cloudflare/workers-oauth-provider for upcoming vulnerabilities?

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