VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

valine: vulnerability history, versions and safety

valine is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 92 releases, from Nov 2018 to Sep 2022. 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 C1 M3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 valine vulnerabilities

Vulert verdict on valine 1.5.3 i

Updated on 23 Oct 2026

Careful: 1.5.3 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.5.3 — affected i
  • Vulnerabilities on record 4 over 3 years · 0 in the last year i
  • Latest disclosure 20 Sep 2022 i
  • Highest CVSS 9.6 i
  • With no published fix 1 i
  • Depended on by 101 packages i
  • Stars 2,227 i
  • OpenSSF scorecard 1/10 i
  • Last release 22 months ago i
  • Licence GPL-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 valine, 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.5.3 15 Dec 2024 M1 GPL-2.0 No Details →
1.5.2 22 Jul 2024 M1 GPL-2.0 No Details →
1.5.1 21 Jul 2022 M1 GPL-2.0 No Details →
1.5.0 24 Jun 2022 M1 GPL-2.0 No Details →
1.4.18 21 Mar 2022 C1 M1 GPL-2.0 No Details →
1.4.17 21 Mar 2022 C1 M1 GPL-2.0 No Details →
1.4.16 19 Oct 2021 C1 M1 GPL-2.0 No Details →
1.4.15 19 Oct 2021 C1 M1 GPL-2.0 No Details →
1.4.14 26 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.13 26 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.12 26 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.11 26 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.10 25 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.9 23 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.8 23 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.7 22 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.6 22 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.5 21 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.4 11 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.3 11 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.2 11 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.1 10 Apr 2020 C1 M2 GPL-2.0 No Details →
1.4.0 10 Apr 2020 C1 M2 GPL-2.0 No Details →
1.3.10 29 Aug 2019 C1 M2 GPL-2.0 No Details →
1.3.9 26 Jun 2019 C1 M2 GPL-2.0 No Details →
1.3.8 26 Jun 2019 C1 M2 GPL-2.0 No Details →
1.3.7 21 Jun 2019 C1 M2 GPL-2.0 No Details →
1.3.6 01 Apr 2019 C1 M2 GPL-2.0 No Details →
1.3.5 29 Mar 2019 C1 M2 GPL-2.0 No Details →
1.3.4 24 Nov 2018 C1 M2 GPL-2.0 No Details →
1.3.3 26 Sep 2018 C1 M3 GPL-2.0 No Details →
1.3.1 03 Sep 2018 C1 M3 GPL-2.0 No Details →
1.3.0 29 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.9 26 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.8 23 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.7 23 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.6 20 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.5 14 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.4 14 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.3 13 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.2 09 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.1 09 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.0 09 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.0-beta2 08 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.0-beta1 07 Jul 2018 C1 M3 GPL-2.0 No Details →
1.2.0-beta 30 Jun 2018 C1 M3 GPL-2.0 No Details →
1.1.9 24 Jun 2018 C1 M3 GPL-2.0 No Details →
1.1.9-rc3 24 Jun 2018 C1 M3 GPL-2.0 No Details →
1.1.9-rc2 15 Jun 2018 C1 M3 GPL-2.0 No Details →
1.1.9-rc1 15 Jun 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta9 29 Mar 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta8 28 Mar 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta7 28 Mar 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta6 28 Mar 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta5 28 Mar 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta4 07 Feb 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta3 20 Jan 2018 C1 M3 GPL-2.0 No Details →
1.1.9-beta2 10 Jan 2018 C1 M3 ISC No Details →
1.1.9-beta1 10 Jan 2018 C1 M3 ISC No Details →
1.1.9-beta 09 Jan 2018 C1 M3 ISC No Details →
1.1.8 29 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc6 27 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc5 27 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc4 27 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc3 26 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc2 22 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc 21 Nov 2017 C1 M3 ISC No Details →
1.1.8-rc1 21 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta9 20 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta8 20 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta7 18 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta6 14 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta5 09 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta4 09 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta3 03 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta2 03 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta1 01 Nov 2017 C1 M3 ISC No Details →
1.1.8-beta 29 Oct 2017 C1 M3 ISC No Details →
1.1.7 20 Oct 2017 C1 M3 ISC No Details →
1.1.6 17 Aug 2017 C1 M3 ISC No Details →
1.1.5 17 Aug 2017 C1 M3 ISC No Details →
1.1.4 13 Aug 2017 C1 M3 ISC No Details →
1.1.3 09 Aug 2017 C1 M3 ISC No Details →
1.1.2 09 Aug 2017 C1 M3 ISC No Details →
1.1.1 08 Aug 2017 C1 M3 ISC No Details →
1.1.0 08 Aug 2017 C1 M3 ISC No Details →
1.0.8 08 Aug 2017 C1 M3 ISC No Details →
1.0.7 08 Aug 2017 C1 M3 ISC No Details →
1.0.6 07 Aug 2017 C1 M3 ISC No Details →
1.0.5 07 Aug 2017 C1 M3 ISC No Details →
1.0.4 07 Aug 2017 C1 M3 ISC No Details →
1.0.3 07 Aug 2017 C1 M3 ISC No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 1
  • 2022 2

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.

03 Vulnerabilities

Recorded vulnerabilities for valine

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-38545: Valine Code Injection Vulnerability 9.6 critical 1.5.0 20 Sep 2022
CVE-2018-19289: Valine - HTML Injection Vulnerability 6.1 medium 1.3.4 21 Nov 2018
CVE-2020-28847: Cross Site Scripting in valine 5.4 medium 1.4.15 06 Apr 2022
CVE-2021-34801: Denial of Service in Valine 5.3 medium No fix published 21 Jun 2021

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 valine

Is valine safe to use?

Vulert records 4 vulnerabilities for valine in npm: 1 critical, 0 high, 3 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is valine's Vulert package health score?

Vulert scores valine 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of valine affected?

Yes. 1.5.3, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of valine should I use?

1.5.3 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 valine have?

4 vulnerabilities are recorded for valine in the npm ecosystem: 1 critical, 0 high, 3 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 valine vulnerabilities disclosed?

0 vulnerabilities were recorded for valine in the last 12 months, and the oldest entry in this database dates to 21 Nov 2018. 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 valine 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 valine for upcoming vulnerabilities?

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