sqlite3 (npm) has 2 known vulnerabilities, the worst rated HIGH. Upgrade to 5.1.5 or later to clear all of them. No malicious-package signal is recorded.
Due to the underlying implementation of .ToString(), it's possible to execute arbitrary JavaScript, or to achieve a denial-of-service, if a binding parameter…
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for sqlite3 (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does sqlite3 have known vulnerabilities?
Yes. CyberXYZ records 2 known vulnerabilities for sqlite3 (npm), the worst rated HIGH. They are GHSA-jqv5-7xpx-qj74, GHSA-9qrh-qjmc-5w2p.
Which version of sqlite3 should I use?
5.1.5 or later clears every advisory recorded for sqlite3 (npm). Check the release you pick before installing it.
How do I check sqlite3 before installing?
Search sqlite3 in CyberXYZ Check at https://cyberxyz.io/check?q=sqlite3. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 07:08 UTC. The most recent advisory here was published 2023-03-13. Updated continuously from NVD, GHSA, OSV and CNA feeds.