CVE-2019-5018

Exp

An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0. A specially crafted SQL command can cause a use after free vulnerability, potentially resulting in remote code execution. An attacker can send a malicious SQL command to trigger this vulnerability.

Published: 2019-05-10 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-5018 is rated High Exploit Risk (83.7/100): CVSS High severity, with high exploitation likelihood (EPSS 6.68%, 93th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +3.75% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2019-5018

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2019-5018

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 2.93% 6.68% +3.75%
2 2026-05-24 2.72% 2.93% +0.21%
3 2026-04-12 — 2.72% —

Full EPSS history (31 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-5018

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]
8.1 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2019-5018

OS Trackers for CVE-2019-5018

vendor priority summary link
alpine high CVE-2019-5018: 1 source package rows (sqlite); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2019-5018
debian not yet assigned CVE-2019-5018 not yet assigned priority: Debian including 1 source packages (sqlite3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-5018
gentoo high CVE-2019-5018: 1 GLSA(s) (201908-09), 1 atom(s) (dev-db/sqlite); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-5018
redhat medium — https://access.redhat.com/security/cve/CVE-2019-5018
suse high CVE-2019-5018 severity important: SUSE including 14 source package names (lemon-3.26.0-11.el8, libsqlite3-0, …), 188 product×package rows across 69 product lines (Magnum Orchestration 7, SLES for SAP Applications 11 SP2, … (69 product lines)): Known Not Affected 183, Fixed 5. https://www.suse.com/security/cve/CVE-2019-5018/
ubuntu low CVE-2019-5018 low priority: Ubuntu including 1 source packages (sqlite3), 7 status rows across 7 suites (bionic, cosmic, disco, eoan, trusty, upstream, xenial): not-affected 4, released 2, needs-triage 1. https://ubuntu.com/security/CVE-2019-5018

Affected software / configurations for CVE-2019-5018

Vendor Product Version Raw CPE
sqlite sqlite 3.26.0 cpe:2.3:a:sqlite:sqlite:3.26.0:*:*:*:*:*:*:*
canonical ubuntu_linux 12.04 cpe:2.3:o:canonical:ubuntu_linux:12.04:*:*:*:-:*:*:*
canonical ubuntu_linux 16.04 cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:esm:*:*:*
canonical ubuntu_linux 18.04 cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 19.04 cpe:2.3:o:canonical:ubuntu_linux:19.04:*:*:*:*:*:*:*
canonical ubuntu_linux 19.10 cpe:2.3:o:canonical:ubuntu_linux:19.10:*:*:*:*:*:*:*

References for CVE-2019-5018

cvelogic Threat Intelligence