Vulnerability Database · npm · devalue · Version

devalue 5.4.2

5.4.2 is affected by 13 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 5 Medium 4 Low 4 Unrated 0

Released 21 Oct 2025 Licence MIT Also known from other sources 13 Newer releases 55 Database updated 23/Oct/2026

Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version

devalue 5.4.2 vulnerabilities

13 vulnerabilities cover devalue 5.4.2. Scroll the table for all of them, or open the full list in the database.

Looking for another version, or everything Vulert holds for devalue?

All versions → Full vulnerability list →

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 5.4.2

Is devalue 5.4.2 vulnerable?

Yes. 13 vulnerabilities in the Vulert database cover devalue 5.4.2: 0 critical, 5 high, 4 medium and 4 low. Each entry above names the fixed version to move to.

Is 5.4.2 the latest release of devalue?

No. 5.4.2 was published 21 Oct 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.