VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@urql/next: vulnerability history, versions and safety

@urql/next is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 14 releases, first recorded in Jan 2024. 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
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 @urql/next vulnerabilities

Vulert verdict on @urql/next 2.0.1 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 2.0.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jan 2024 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Stars 8,980 i
  • Last release 4 months ago 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 @urql/next, 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
2.0.1 15 Jun 2026 none MIT — Details →
2.0.0 09 Aug 2025 none MIT — Details →
2.0.0-canary-b981b388ee9ed0066399a632aad6b84559f014a6 09 Aug 2025 none MIT — Details →
2.0.0-canary-d3b019d51905c1c8b22be9ea1d9fe9ca4335a46c 09 Aug 2025 none MIT — Details →
2.0.0-canary-b2d8b993af4abb0ffc5c5284b90aca56c527f045 29 Jun 2025 none MIT — Details →
1.1.5 03 Mar 2025 none MIT — Details →
1.1.5-canary-573944cea80f766668d3b9d8aa1afd2c50d744a4 03 Mar 2025 none MIT — Details →
1.1.4 04 Feb 2025 none MIT — Details →
1.1.4-canary-dbc7a5b8101d297c7f8ca961096d08d503376522 04 Feb 2025 none MIT — Details →
1.1.3 06 Nov 2024 none MIT — Details →
1.1.3-canary-d51641036e060d63b7810778ea73c6d0c0d3fd2c 06 Nov 2024 none MIT — Details →
1.1.2 14 Sep 2024 none MIT — Details →
1.1.2-canary-a19f8303af8e1a3dcc98b9d3db48050a019b99c2 14 Sep 2024 none MIT — Details →
1.1.2-canary-7c8c5e4700b22a12079cf067a5c0cad42885efa7 14 Sep 2024 none MIT — Details →
1.1.2-canary-fcd7e6055c8a945b85a1e35e4813d09a428d0405 14 Sep 2024 none MIT — Details →
1.1.2-canary-5886b511 14 Sep 2024 none MIT — Details →
1.1.2-canary-885a4392 14 Sep 2024 none MIT — Details →
1.1.2-canary-63082110 14 Sep 2024 none MIT — Details →
1.1.2-canary-b9f34fd1 13 Sep 2024 none MIT — Details →
1.1.2-canary-102cc0d7 13 Sep 2024 none MIT — Details →
1.1.2-canary-b039ae58 13 Sep 2024 none MIT — Details →
1.1.1 30 Jan 2024 none MIT — Details →
1.1.1-canary-30d22e27 30 Jan 2024 H1 MIT Yes Details →
1.1.1-canary-4b7011b7 30 Jan 2024 H1 MIT Yes Details →
1.1.1-canary-1d6be509 10 Dec 2023 H1 MIT Yes Details →
1.1.1-canary-765bae94 10 Dec 2023 H1 MIT Yes Details →
1.1.1-canary-fa692c1c 06 Dec 2023 H1 MIT Yes Details →
1.1.0 19 Oct 2023 H1 MIT Yes Details →
1.1.0-canary-812385d4 19 Oct 2023 H1 MIT Yes Details →
1.1.0-canary-423897f9 19 Oct 2023 H1 MIT Yes Details →
1.0.1-canary-f66de5be 19 Oct 2023 H1 MIT Yes Details →
1.0.0 21 Jul 2023 H1 MIT Yes Details →
1.0.0-canary-d6bdd72e 21 Jul 2023 H1 MIT Yes Details →
1.0.0-canary-889ca4db 21 Jul 2023 H1 MIT Yes Details →
1.0.0-beta.2 06 Jun 2023 H1 MIT Yes Details →
1.0.0-beta.1 31 May 2023 H1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for @urql/next

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-24556: @urql/next Cross-site Scripting vulnerability 7.2 high 1.1.1 30 Jan 2024

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 @urql/next

Is @urql/next safe to use?

Vulert records 1 vulnerabilities for @urql/next 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 @urql/next's Vulert package health score?

Vulert scores @urql/next 81/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 @urql/next affected?

No. 2.0.1, 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 @urql/next should I use?

2.0.1 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 @urql/next have?

1 vulnerability is recorded for @urql/next 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 @urql/next vulnerabilities disclosed?

0 vulnerabilities were recorded for @urql/next in the last 12 months, and the oldest entry in this database dates to 30 Jan 2024. 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 @urql/next 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 @urql/next for upcoming vulnerabilities?

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