VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

generator-jhipster: vulnerability history, versions and safety

generator-jhipster is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 119 releases, from Sep 2019 to 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
7 vulnerabilities recorded C1 H5 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all generator-jhipster vulnerabilities

Vulert verdict on generator-jhipster 9.4.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 9.4.0 — unaffected i
  • Vulnerabilities on record 7 over 7 years · 2 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 112 packages i
  • Stars 22,465 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago 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 generator-jhipster, 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
9.4.0 18 Sep 2026 none Apache-2.0 — Details →
9.3.0 30 Aug 2026 H2 Apache-2.0 Yes Details →
9.2.0 10 Jul 2026 H2 Apache-2.0 Yes Details →
9.1.0 27 May 2026 H2 Apache-2.0 Yes Details →
9.0.0 11 Mar 2026 H2 Apache-2.0 Yes Details →
9.0.0-beta.3 05 Feb 2026 H2 Apache-2.0 Yes Details →
9.0.0-beta.2 30 Jan 2026 H2 Apache-2.0 Yes Details →
9.0.0-beta.1 29 Jan 2026 H2 Apache-2.0 Yes Details →
9.0.0-beta.0 06 Dec 2025 H2 Apache-2.0 Yes Details →
8.11.0 07 May 2025 H2 Apache-2.0 Yes Details →
8.10.0 01 Apr 2025 H2 Apache-2.0 Yes Details →
8.9.0 08 Feb 2025 H2 Apache-2.0 Yes Details →
8.8.0 23 Dec 2024 H2 L1 Apache-2.0 Yes Details →
8.7.3 30 Oct 2024 H2 L1 Apache-2.0 Yes Details →
8.7.2 28 Oct 2024 H2 L1 Apache-2.0 Yes Details →
8.7.1 21 Sep 2024 H2 L1 Apache-2.0 Yes Details →
8.7.0 27 Aug 2024 H2 L1 Apache-2.0 Yes Details →
8.6.0 24 Jun 2024 H2 L1 Apache-2.0 Yes Details →
8.5.0 31 May 2024 H2 L1 Apache-2.0 Yes Details →
8.4.0 30 Apr 2024 H2 L1 Apache-2.0 Yes Details →
8.3.0 09 Apr 2024 H2 L1 Apache-2.0 Yes Details →
8.2.1 20 Mar 2024 H2 L1 Apache-2.0 Yes Details →
8.2.0 20 Mar 2024 H2 L1 Apache-2.0 Yes Details →
8.1.0 11 Dec 2023 H2 L1 Apache-2.0 Yes Details →
8.0.0 02 Nov 2023 H2 L1 Apache-2.0 Yes Details →
8.0.0-rc.1 14 Oct 2023 H2 L1 Apache-2.0 Yes Details →
8.0.0-beta.3 05 Sep 2023 H2 L1 Apache-2.0 Yes Details →
7.9.4 05 Sep 2023 H2 L1 Apache-2.0 Yes Details →
8.0.0-beta.2 12 Jul 2023 H2 L1 Apache-2.0 Yes Details →
8.0.0-beta.1 11 Jun 2023 H2 L1 Apache-2.0 Yes Details →
7.9.3 02 Sep 2022 H2 L1 Apache-2.0 Yes Details →
7.9.2 03 Aug 2022 H2 L1 Apache-2.0 Yes Details →
7.9.1 03 Aug 2022 H2 L1 Apache-2.0 Yes Details →
7.9.0 31 Jul 2022 H2 L1 Apache-2.0 Yes Details →
7.8.1 07 Apr 2022 H2 L1 Apache-2.0 Yes Details →
7.8.0 01 Apr 2022 H3 L1 Apache-2.0 Yes Details →
7.7.0 27 Feb 2022 H3 L1 Apache-2.0 Yes Details →
7.6.0 23 Jan 2022 H3 L1 Apache-2.0 Yes Details →
7.5.0 02 Jan 2022 H3 L1 Apache-2.0 Yes Details →
7.4.1 03 Dec 2021 H3 L1 Apache-2.0 Yes Details →
7.4.0 19 Nov 2021 H3 L1 Apache-2.0 Yes Details →
7.3.1 19 Oct 2021 H3 L1 Apache-2.0 Yes Details →
7.3.0 08 Oct 2021 H3 L1 Apache-2.0 Yes Details →
7.2.0 14 Sep 2021 H3 L1 Apache-2.0 Yes Details →
7.1.0 18 Jun 2021 H3 L1 Apache-2.0 Yes Details →
7.0.1 02 Apr 2021 H3 L1 Apache-2.0 Yes Details →
7.0.0 21 Mar 2021 H3 L1 Apache-2.0 Yes Details →
7.0.0-beta.1 17 Jan 2021 H1 L1 Apache-2.0 Yes Details →
7.0.0-beta.0 21 Dec 2020 H1 L1 Apache-2.0 Yes Details →
6.10.5 07 Nov 2020 H1 L1 Apache-2.0 Yes Details →
6.10.4 18 Oct 2020 H1 L1 Apache-2.0 Yes Details →
6.10.3 20 Sep 2020 H1 L1 Apache-2.0 Yes Details →
6.10.2 20 Sep 2020 H1 L1 Apache-2.0 Yes Details →
6.10.1 04 Jul 2020 H1 L1 Apache-2.0 Yes Details →
6.10.0 28 Jun 2020 H1 L1 Apache-2.0 Yes Details →
6.9.1 01 Jun 2020 H1 L1 Apache-2.0 Yes Details →
6.9.0 17 May 2020 H1 L1 Apache-2.0 Yes Details →
6.8.0 08 Mar 2020 H1 L1 Apache-2.0 Yes Details →
6.7.1 12 Feb 2020 H1 L1 Apache-2.0 Yes Details →
6.7.0 06 Feb 2020 H1 L1 Apache-2.0 Yes Details →
6.6.0 22 Dec 2019 H1 L1 Apache-2.0 Yes Details →
6.5.1 19 Nov 2019 H1 L1 Apache-2.0 Yes Details →
6.5.0 10 Nov 2019 H1 L1 Apache-2.0 Yes Details →
6.4.1 11 Oct 2019 H1 L1 Apache-2.0 Yes Details →
6.4.0 10 Oct 2019 H1 L1 Apache-2.0 Yes Details →
6.3.1 20 Sep 2019 H1 L1 Apache-2.0 Yes Details →
6.3.0 13 Sep 2019 H2 L1 Apache-2.0 Yes Details →
6.2.0 01 Aug 2019 C1 H2 L1 Apache-2.0 Yes Details →
6.1.2 23 Jun 2019 C1 H2 L1 Apache-2.0 Yes Details →
6.1.1 21 Jun 2019 C1 H2 L1 Apache-2.0 Yes Details →
6.1.0 11 Jun 2019 C1 H2 L1 Apache-2.0 Yes Details →
6.0.1 10 May 2019 C1 H2 L1 Apache-2.0 Yes Details →
6.0.0 02 May 2019 C1 H2 L1 Apache-2.0 Yes Details →
6.0.0-beta.0 04 Apr 2019 C1 H2 L1 Apache-2.0 Yes Details →
5.8.2 28 Feb 2019 C1 H2 L1 Apache-2.0 Yes Details →
5.8.1 29 Jan 2019 C1 H2 L1 Apache-2.0 Yes Details →
5.8.0 25 Jan 2019 C1 H2 L1 Apache-2.0 Yes Details →
5.7.2 21 Dec 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.7.1 14 Dec 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.7.0 13 Nov 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.6.1 05 Nov 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.6.0 02 Nov 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.5.0 16 Oct 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.4.2 07 Oct 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.4.1 04 Oct 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.4.0 03 Oct 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.3.4 17 Sep 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.3.3 17 Sep 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.3.2 17 Sep 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.3.1 05 Sep 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.3.0 03 Sep 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.2.1 16 Aug 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.2.0 13 Aug 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.1.0 12 Jul 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.0.2 05 Jul 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.0.1 23 Jun 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.0.0 20 Jun 2018 C1 H2 L1 Apache-2.0 Yes Details →
4.14.5 19 Jun 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.0.0-beta.3 18 Jun 2018 C1 H2 L1 Apache-2.0 Yes Details →
5.0.0-beta.2 13 Jun 2018 C1 H2 L1 Apache-2.0 Yes Details →
4.14.4 11 May 2018 C1 H2 L1 — Yes Details →
5.0.0-beta.1 03 May 2018 C1 H2 L1 — Yes Details →
4.14.3 10 Apr 2018 C1 H2 L1 — Yes Details →
4.14.2 06 Apr 2018 C1 H2 L1 — Yes Details →
5.0.0-beta.0 03 Apr 2018 C1 H2 L1 — Yes Details →
4.14.1 27 Feb 2018 C1 H2 L1 — Yes Details →
4.14.0 30 Jan 2018 C1 H2 L1 — Yes Details →
4.13.3 09 Jan 2018 C1 H2 L1 — Yes Details →
4.13.2 04 Jan 2018 C1 H2 L1 — Yes Details →
4.13.1 27 Dec 2017 C1 H2 L1 — Yes Details →
4.13.0 14 Dec 2017 C1 H2 L1 — Yes Details →
4.12.0 08 Dec 2017 C1 H2 L1 — Yes Details →
4.11.1 26 Nov 2017 C1 H2 L1 — Yes Details →
4.11.0 24 Nov 2017 C1 H2 L1 — Yes Details →
4.10.2 27 Oct 2017 C1 H2 L1 — Yes Details →
4.10.1 25 Oct 2017 C1 H2 L1 — Yes Details →
4.10.0 17 Oct 2017 C1 H2 L1 — Yes Details →
4.9.0 28 Sep 2017 C1 H2 L1 — Yes Details →
4.8.2 15 Sep 2017 C1 H2 L1 — Yes Details →
4.8.1 13 Sep 2017 C1 H2 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2
  • 2022 1
  • 2023 1
  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for generator-jhipster

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Vulnerability in generator-jhipster: Account Takeover and Privilege Escalation 9.8 critical 6.3.0 13 Sep 2019
CVE-2026-107375: SQL Injection in JHipster-Generated Reactive Applications 8.8 high 9.4.0 08 Oct 2026
Insecure Repository Configuration in generator-jhipster 8.1 high 6.3.1 23 Sep 2019
CVE-2022-24815: SQL Injection in generator-jhipster 8.1 high 7.8.1 07 Apr 2022
CVE-2026-107303: JHipster Applications Vulnerable to Stored XSS via Unrestricted Blob ContentType 7.6 high 9.4.0 08 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 generator-jhipster

Is generator-jhipster safe to use?

Vulert records 7 vulnerabilities for generator-jhipster in npm: 1 critical, 5 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 generator-jhipster's Vulert package health score?

Vulert scores generator-jhipster 79/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 generator-jhipster affected?

No. 9.4.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 generator-jhipster should I use?

9.4.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 generator-jhipster have?

7 vulnerabilities are recorded for generator-jhipster in the npm ecosystem: 1 critical, 5 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 generator-jhipster vulnerabilities disclosed?

2 vulnerabilities were recorded for generator-jhipster in the last 12 months, and the oldest entry in this database dates to 13 Sep 2019. 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 generator-jhipster 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 generator-jhipster for upcoming vulnerabilities?

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