VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

devalue: vulnerability history, versions and safety

devalue is a package in the npm ecosystem. Vulert records 16 vulnerabilities for it across 49 releases, from Aug 2025 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
16 vulnerabilities recorded H8 M4 L4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
15 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all devalue vulnerabilities

Vulert verdict on devalue 6.0.3 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 6.0.3 — unaffected i
  • Vulnerabilities on record 16 over 1 year · 15 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 372 packages i
  • Stars 2,810 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 devalue, 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
6.0.3 13 Oct 2026 none MIT — Details →
6.0.2 22 Sep 2026 none MIT — Details →
6.0.1 21 Sep 2026 none MIT — Details →
6.0.0 19 Sep 2026 none MIT — Details →
5.9.4 18 Sep 2026 none MIT — Details →
5.9.3 18 Sep 2026 none MIT — Details →
5.9.2 27 Aug 2026 H4 M2 L1 MIT Yes Details →
5.9.1 20 Aug 2026 H4 M3 L1 MIT Yes Details →
5.9.0 30 Jul 2026 H4 M3 L1 MIT Yes Details →
5.8.2 20 Jul 2026 H4 M3 L1 MIT Yes Details →
5.8.1 14 May 2026 H4 M3 L1 MIT Yes Details →
5.8.0 30 Apr 2026 H5 M3 L1 MIT Yes Details →
5.7.1 08 Apr 2026 H4 M3 L1 MIT Yes Details →
5.7.0 06 Apr 2026 H4 M3 L1 MIT Yes Details →
5.6.4 11 Mar 2026 H4 M3 L1 MIT Yes Details →
5.6.3 18 Feb 2026 H4 M4 L2 MIT Yes Details →
5.6.2 15 Jan 2026 H3 M4 L4 MIT Yes Details →
5.6.1 11 Dec 2025 H5 M4 L4 MIT Yes Details →
5.6.0 08 Dec 2025 H5 M4 L4 MIT Yes Details →
5.5.0 12 Nov 2025 H5 M4 L4 MIT Yes Details →
5.4.2 21 Oct 2025 H5 M4 L4 MIT Yes Details →
5.4.1 15 Oct 2025 H5 M4 L4 MIT Yes Details →
5.4.0 15 Oct 2025 H5 M4 L4 MIT Yes Details →
5.3.2 26 Aug 2025 H5 M4 L4 MIT Yes Details →
5.3.1 26 Aug 2025 H6 M4 L4 MIT Yes Details →
5.3.0 26 Aug 2025 H6 M4 L4 MIT Yes Details →
5.2.0 26 Aug 2025 H5 M4 L4 MIT Yes Details →
5.1.1 25 Sep 2024 H5 M4 L4 MIT Yes Details →
5.1.0 25 Sep 2024 H5 M4 L4 MIT Yes Details →
5.0.0 19 Apr 2024 H3 M4 L4 MIT Yes Details →
4.3.3 19 Apr 2024 H3 M4 L4 MIT Yes Details →
4.3.2 22 May 2023 H3 M4 L4 MIT Yes Details →
4.3.1 14 May 2023 H3 M4 L4 MIT Yes Details →
4.3.0 10 Feb 2023 H3 M4 L4 MIT Yes Details →
4.2.3 30 Jan 2023 H3 M4 L4 MIT Yes Details →
4.2.2 11 Jan 2023 H3 M4 L4 MIT Yes Details →
4.2.1 10 Jan 2023 H3 M4 L4 MIT Yes Details →
4.2.0 02 Nov 2022 H3 M4 L4 MIT Yes Details →
4.1.0 01 Nov 2022 H3 M4 L4 MIT Yes Details →
4.0.1 17 Oct 2022 H3 M4 L4 MIT Yes Details →
4.0.0 03 Oct 2022 H3 M4 L4 MIT Yes Details →
3.1.3 01 Sep 2022 H3 M4 L4 MIT Yes Details →
3.1.2 26 Aug 2022 H3 M4 L4 MIT Yes Details →
3.1.1 26 Aug 2022 H3 M4 L4 MIT Yes Details →
3.1.0 26 Aug 2022 H3 M4 L4 MIT Yes Details →
3.0.1 26 Aug 2022 H3 M4 L4 MIT Yes Details →
2.0.1 29 Nov 2019 H3 M4 L4 MIT Yes Details →
2.0.0 18 Jun 2019 H3 M4 L4 MIT Yes Details →
1.1.1 10 Jun 2019 H3 M4 L4 non-standard Yes Details →
1.1.0 26 Oct 2018 H3 M4 L4 non-standard Yes Details →
1.0.4 31 Jul 2018 H3 M4 L4 non-standard Yes Details →
1.0.3 27 Mar 2018 H3 M4 L4 non-standard Yes Details →
1.0.2 26 Mar 2018 H3 M4 L4 non-standard Yes Details →
1.0.1 10 Mar 2018 H3 M4 L4 non-standard Yes Details →
1.0.0 10 Mar 2018 H3 M4 L4 non-standard Yes Details →

All 55 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 1
  • 2026 15

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

03 Vulnerabilities

Recorded vulnerabilities for devalue

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unhandled Promise Rejection in devalue Package: A Critical Vulnerability 8.2 high 5.9.3 01 Oct 2026
High Severity Vulnerability in devalue: Quadratic Expansion in uneval 8.2 high 5.9.3 01 Oct 2026
Critical ArrayBuffer Reviver Bypass in devalue Package 8.2 high 5.9.3 01 Oct 2026
CVE-2025-57820: devalue Package Prototype Pollution Vulnerability 7.9 high 5.3.2 26 Aug 2025
CVE-2026-22774: Devalue Package Denial of Service Vulnerability Due to Memory Exhaustion 7.5 high 5.6.2 15 Jan 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 devalue

Is devalue safe to use?

Vulert records 16 vulnerabilities for devalue in npm: 0 critical, 8 high, 4 medium and 4 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 devalue's Vulert package health score?

Vulert scores devalue 65/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).

Is the latest version of devalue affected?

No. 6.0.3, 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 devalue have?

16 vulnerabilities are recorded for devalue in the npm ecosystem: 0 critical, 8 high, 4 medium and 4 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new devalue vulnerabilities disclosed?

15 vulnerabilities were recorded for devalue in the last 12 months, and the oldest entry in this database dates to 26 Aug 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 devalue 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 devalue for upcoming vulnerabilities?

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