VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

graphql-shield: vulnerability history, versions and safety

graphql-shield is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 58 releases, first recorded in Sep 2020. 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 L1
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 graphql-shield vulnerabilities

Vulert verdict on graphql-shield 7.6.5 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release 7.6.5 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 56 packages i
  • Stars 3,577 i
  • OpenSSF scorecard 3/10 i
  • Last release 47 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 graphql-shield, 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
8.0.0-alpha-20221215200711-24c1953 15 Dec 2022 none MIT — Details →
8.0.0-alpha-20221214190806-3953778 14 Dec 2022 none MIT — Details →
8.0.0-alpha-20221214185453-335ce4c 14 Dec 2022 none MIT — Details →
8.0.0-alpha-20221127163606-0a537b9 27 Nov 2022 none MIT — Details →
7.6.5 22 Nov 2022 none MIT — Details →
7.6.5-alpha-20221122185642-d59dda0 22 Nov 2022 none MIT — Details →
7.6.4 28 Oct 2022 none MIT — Details →
7.6.3 17 Oct 2022 none MIT — Details →
7.6.3-alpha-20221013161836-7522a9f 13 Oct 2022 none MIT — Details →
7.6.3-alpha-20221013154153-ccafe90 13 Oct 2022 none MIT — Details →
7.6.3-alpha-20221013120629-ebfd83d 13 Oct 2022 none MIT — Details →
7.6.3-alpha-20221010152516-b34c741 10 Oct 2022 none MIT — Details →
7.6.3-alpha-20221010152214-fe69b7a 10 Oct 2022 none MIT — Details →
7.6.3-alpha-20221010012441-56c6c85 10 Oct 2022 none MIT — Details →
7.6.3-alpha-20221009092723-76b0373 09 Oct 2022 none MIT — Details →
7.6.3-alpha-20221009084405-76b0373 09 Oct 2022 none MIT — Details →
7.6.3-alpha-20221007172208-7dbe09d 07 Oct 2022 none MIT — Details →
7.6.3-alpha-20221003195722-1106a3d 03 Oct 2022 none MIT — Details →
0.0.0-alpha-20221003194237 03 Oct 2022 L1 MIT Yes Details →
7.6.2 01 Oct 2022 none MIT — Details →
7.6.1 01 Oct 2022 none MIT — Details →
7.6.0 01 Oct 2022 none MIT — Details →
7.5.0 13 Jan 2021 none MIT — Details →
7.4.4 16 Dec 2020 none MIT — Details →
7.4.3 03 Dec 2020 none MIT — Details →
7.4.2 23 Nov 2020 none MIT — Details →
7.4.1 19 Nov 2020 none MIT — Details →
7.4.0 31 Oct 2020 none MIT — Details →
7.3.8 28 Oct 2020 none MIT — Details →
7.3.7 08 Oct 2020 none MIT — Details →
7.3.6 11 Sep 2020 none MIT — Details →
7.3.5 20 Aug 2020 none MIT — Details →
7.3.4 14 Aug 2020 none MIT — Details →
7.3.3 03 Aug 2020 none MIT — Details →
7.3.2 12 Jun 2020 none MIT — Details →
7.3.1 12 Jun 2020 none MIT — Details →
7.3.0 14 May 2020 none MIT — Details →
7.2.6 22 Apr 2020 none MIT — Details →
7.2.5 17 Apr 2020 none MIT — Details →
7.2.4 13 Apr 2020 none MIT — Details →
7.2.3 09 Apr 2020 none MIT — Details →
7.2.2 01 Apr 2020 none MIT — Details →
7.2.1 18 Mar 2020 none MIT — Details →
7.2.0 12 Mar 2020 none MIT — Details →
7.1.0 11 Mar 2020 none MIT — Details →
7.0.14 24 Feb 2020 none MIT — Details →
7.0.13 18 Feb 2020 none MIT — Details →
7.0.12 14 Feb 2020 none MIT — Details →
7.0.11 08 Feb 2020 none MIT — Details →
7.0.10 05 Feb 2020 none MIT — Details →
7.0.9 28 Jan 2020 none MIT — Details →
7.0.8 25 Jan 2020 none MIT — Details →
7.0.7 30 Dec 2019 none MIT — Details →
7.0.6 20 Dec 2019 none MIT — Details →
7.0.5 16 Dec 2019 none MIT — Details →
7.0.4 27 Nov 2019 none MIT — Details →
7.0.3 27 Nov 2019 none MIT — Details →
7.0.2 05 Nov 2019 none MIT — Details →
7.0.1 01 Nov 2019 none MIT — Details →
7.0.0 24 Oct 2019 none MIT — Details →
6.1.0 07 Sep 2019 none MIT — Details →
6.0.7 06 Sep 2019 none MIT — Details →
6.0.6 26 Aug 2019 none MIT — Details →
6.0.5 20 Aug 2019 L1 MIT Yes Details →
6.0.4 16 Jul 2019 L1 MIT Yes Details →
6.0.3 08 Jul 2019 L1 MIT Yes Details →
6.0.2 01 Jul 2019 L1 MIT Yes Details →
6.0.1 01 Jul 2019 L1 MIT Yes Details →
6.0.0 30 Jun 2019 L1 MIT Yes Details →
5.7.3 29 Jun 2019 L1 MIT Yes Details →
5.7.2 29 Jun 2019 L1 MIT Yes Details →
5.7.1 21 Jun 2019 L1 MIT Yes Details →
5.7.0 20 Jun 2019 L1 MIT Yes Details →
5.6.2 20 Jun 2019 L1 MIT Yes Details →
5.6.1 19 Jun 2019 L1 MIT Yes Details →
5.6.0 19 Jun 2019 L1 MIT Yes Details →
5.5.0 19 Jun 2019 L1 MIT Yes Details →
5.4.0 19 Jun 2019 L1 MIT Yes Details →
5.3.8 11 Jun 2019 L1 MIT Yes Details →
5.3.7 10 Jun 2019 L1 MIT Yes Details →
5.3.6 04 Jun 2019 L1 MIT Yes Details →
5.3.5 02 May 2019 L1 MIT Yes Details →
5.3.4 18 Apr 2019 L1 MIT Yes Details →
5.3.3 12 Apr 2019 L1 MIT Yes Details →
5.3.2 09 Apr 2019 L1 MIT Yes Details →
5.3.1 14 Mar 2019 L1 MIT Yes Details →
5.3.0 18 Feb 2019 L1 MIT Yes Details →
5.2.0 15 Feb 2019 L1 MIT Yes Details →
5.1.3 11 Feb 2019 L1 MIT Yes Details →
5.1.2 06 Feb 2019 L1 MIT Yes Details →
5.1.1 04 Feb 2019 L1 MIT Yes Details →
5.1.0 22 Dec 2018 L1 MIT Yes Details →
5.0.1 18 Dec 2018 L1 MIT Yes Details →
5.0.0 18 Dec 2018 L1 MIT Yes Details →
4.1.2 10 Dec 2018 L1 MIT Yes Details →
4.1.1 09 Dec 2018 L1 MIT Yes Details →
4.1.0 02 Nov 2018 L1 MIT Yes Details →
4.0.1 26 Oct 2018 L1 MIT Yes Details →
4.0.0 26 Oct 2018 L1 MIT Yes Details →
3.2.5 03 Oct 2018 L1 MIT Yes Details →
3.2.4 26 Sep 2018 L1 — Yes Details →
3.2.3 20 Sep 2018 L1 — Yes Details →
3.2.2 15 Sep 2018 L1 — Yes Details →
3.2.1 05 Sep 2018 L1 — Yes Details →
3.2.0 05 Sep 2018 L1 — Yes Details →
3.1.2 03 Sep 2018 L1 — Yes Details →
3.1.1 30 Aug 2018 L1 — Yes Details →
3.1.0 30 Aug 2018 L1 — Yes Details →
3.0.1 29 Aug 2018 L1 — Yes Details →
3.0.0 28 Aug 2018 L1 — Yes Details →
3.0.0-beta 28 Aug 2018 L1 — Yes Details →
2.2.7 14 Aug 2018 L1 — Yes Details →
2.2.6 10 Jul 2018 L1 — Yes Details →
2.2.5 27 Jun 2018 L1 — Yes Details →
2.2.4 25 Jun 2018 L1 — Yes Details →
2.2.3 20 Jun 2018 L1 — Yes Details →
2.2.2 19 Jun 2018 L1 — Yes Details →
2.2.1 19 Jun 2018 L1 — Yes Details →
2.2.0 18 Jun 2018 L1 — Yes Details →
2.1.5 17 Jun 2018 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 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 graphql-shield

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Authorization Bypass in graphql-shield N/A low 6.0.6 03 Sep 2020

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 graphql-shield

Is graphql-shield safe to use?

Vulert records 1 vulnerabilities for graphql-shield in npm: 0 critical, 0 high, 0 medium and 1 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 graphql-shield's Vulert package health score?

Vulert scores graphql-shield 71/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 graphql-shield affected?

No. 7.6.5, 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 graphql-shield should I use?

7.6.5 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 graphql-shield have?

1 vulnerability is recorded for graphql-shield in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new graphql-shield vulnerabilities disclosed?

0 vulnerabilities were recorded for graphql-shield in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 graphql-shield 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 graphql-shield for upcoming vulnerabilities?

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