Vulnerability Database · npm · veval · Version

veval 1.0.1

1.0.1 is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.0.1.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 31 Mar 2019 Status latest release Licence GPL-3.0 Also known from other sources 1 Newer releases 2 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

veval 1.0.1 vulnerabilities

1 vulnerability cover veval 1.0.1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Sandbox Breakout / Arbitrary Code Execution in veval N/A critical No fix published 04 Sep 2020

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

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 veval 1.0.1

Is veval 1.0.1 vulnerable?

Yes. 1 vulnerability in the Vulert database cover veval 1.0.1: 1 critical, 0 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.0.1, and each entry above names the fixed version to move to.

Which version of veval should I use instead of 1.0.1?

1.0.1 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 1.0.1 the latest release of veval?

Yes. 1.0.1 is the current release, published 31 Mar 2019. Staying on the current line is what keeps you inside the publisher's fixes.

How do I monitor veval for upcoming vulnerabilities?

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